News for hackers. Stuff that matters.
Re:Introducing Libscore: A PageRank for JavaScript Libraries by billyhoffman on Tuesday December 16, 2014 @11:25PM (#8761071)
"Before Libscore, front-end developers only had Github star counts as a proxy for their library’s success."

Uhhh no. Before Libscore, we only had Wapanalyzer and BuiltWith and Alexa and Ghostry and countless other "crawl and aggregate stats data" services.

Cool idea and all, but kinda silly to make claims like this.

Re:Introducing Libscore: A PageRank for JavaScript Libraries by purpleturtle on Wednesday December 17, 2014 @12:17AM (#8761181)
builtwith doesn't show all js libs. it just whitelists the top 20 i believe. looks like Wapanalyzer might be similar.

alexa is also unrelated to broad js penetration detection.

not sure how ghostery is relevant.

the novelty of libscore is that it detects all js libs (even brand new ones with only 20 sites using it); doesn't use a dumb whitelist filter.

Re:Introducing Libscore: A PageRank for JavaScript Libraries by AdamTReineke on Wednesday December 17, 2014 @04:33AM (#8761691)
Great example is to look at Microsoft.com and see a bunch of tiny "MS" prefixed libraries that probably only exist on their web properties.