Introducing Libscore: A PageRank for JavaScript Libraries

Re:Introducing Libscore: A PageRank for JavaScript Libraries by mynegation on Tuesday December 16, 2014 @05:46PM (#8760075)

It is not PageRank, it is Altavista for JavaScript libraries. PageRank would be computing PageRank on JavaScript library dependency graph.

[ Parent | on HN ]

Re:Introducing Libscore: A PageRank for JavaScript Libraries by hyp0 on Tuesday December 16, 2014 @07:25PM (#8760426)

I was thinking actual PageRank would be interesting, ranking libraries by who uses what, transitively.

Might be nice to include weightings of app usage by users and downloads (because apps aren't used by other libraries), but just sticking to code-used-by-code could be interesting:

So, "one lib/app, one vote" (weighted by how much it is used by other libs/apps), measures coders' evaluation, not app-users'.

And not have the search part (which PageRank ranks), just the ranking - e.g. a top 10

[ Parent | on HN ]

Re:Introducing Libscore: A PageRank for JavaScript Libraries by purpleturtle on Tuesday December 16, 2014 @05:55PM (#8760109)

Yeah, the submitter (unaffiliated) came up with that slogan on his/her own. Happy to have admins here change the title if they're willing?

[ Parent | on HN ]

Re:Introducing Libscore: A PageRank for JavaScript Libraries by egeozcan on Wednesday December 17, 2014 @07:32AM (#8762054)

A limited way to achieve PageRank-like statistics could be parsing all the js package repositories (like npm, bower, atmosphere, etc.)

[ Parent | on HN ]

Re:Introducing Libscore: A PageRank for JavaScript Libraries by Kiro on Wednesday December 17, 2014 @04:24AM (#8761662)

Just FYI: The article doesn't even mention PageRank.

[ Parent | on HN ]