News for hackers. Stuff that matters.

purpleturtle

Right — that's how I interpreted it. There are still two companies that are larger in San Francisco.
> "We have quickly become the market leader in San Francisco."

This is an odd statement since I know there are at least two direct competitors who are far larger.

Re:Libscore: View the growth of open source libraries on Monday June 22, 2015 @04:17PM (#9760899)
I'm involved in the project if anyone has comments/suggestions.
Re:How to deal with startup competition on Wednesday April 29, 2015 @05:50PM (#9462073)
Author here if anyone has further advice for me to weave into the post.
Re:Webflow's YC acceptance story [video] on Monday March 23, 2015 @06:40PM (#9253786)
Video producer here. Would anyone be interested in seeing more YC founder stories told on film?
Re:Introducing Libscore: A PageRank for JavaScript Libraries 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 on Tuesday December 16, 2014 @08:03PM (#8760542)
Unlike celebrity culture, popularity in the open source world translates to actual impact on the web. As an author of a popular library, your code plays a direct part in how other developers structure their codebase, and -- depending on the library -- the end user experience.

And, yeah, impact/change/popularity (whatever you want to call it) is certainly a main reason behind releasing and maintaining open source software. Perhaps other dominant reasons include giving users differently opionionated alternatives that better suit their workflow, advancing the technical know-how of a field, and simply experimenting for expressiveness' sake.

Re:Introducing Libscore: A PageRank for JavaScript Libraries 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?
Re:Introducing Libscore: A PageRank for JavaScript Libraries on Tuesday December 16, 2014 @05:31PM (#8760002)
Exactly. That's why we removed any mention of a "score" from the copywriting before launching. We realized how vague a score could be. We focus on site counts now, since they're raw/unfiltered data.
Re:Introducing Libscore: A PageRank for JavaScript Libraries on Tuesday December 16, 2014 @05:09PM (#8759893)
npm actually publishes its own top lists.

what's interesting about the work we've done on libscore is that it shows the end result -- whether a lib was actually ultimately used on a site. npm can tell you download stats, but that's where its data ends.

Re:Introducing Libscore: A PageRank for JavaScript Libraries on Tuesday December 16, 2014 @05:07PM (#8759886)
Cleaning a few things up first :) Star the repo and stay tuned for an update.
Re:Introducing Libscore: A PageRank for JavaScript Libraries on Tuesday December 16, 2014 @04:28PM (#8759633)
Search for "React", which is the variable name React exposes itself under. It's also on the trending data page.
Re:Introducing Libscore: A PageRank for JavaScript Libraries on Tuesday December 16, 2014 @03:17PM (#8759175)
Good points :)

The problem was that fuzzy search would have been technically overwhelming to implement due to the size of our data sets (1 million sites * avg. # of leaked global variables). Also, it would have resulted in a lot of confusing matches because of how arbitrary JavaScript variable names are.

Keeping it to one-for-one case sensitive lookups was the only way to clearly express searching behavior and return accurate data every time. The downside is that we force people to read our homepage how-to to learn how to use it :)

Re:Libscore on Tuesday December 16, 2014 @02:52PM (#8758979)
One of the creators of Libscore here. I want to sincerely thank Stripe for making this project happen. I am still elated that they were willing to back this crazy idea of mine.

Libscore isn't perfect, but it sufficiently serves its purpose of competitive analysis. I've written more about the intentions of the project, including a thorough analysis of its downsides, here: https://medium.com/@Shapiro/introducing-libscore-com-be93165...

Re:Velocity.js on Friday November 28, 2014 @11:19AM (#8671323)
Fear not. Your performance concerns are mostly unwarranted (creator or Velocity here). Here are some articles to consider reading that help debunk this myth:

http://css-tricks.com/myth-busting-css-animations-vs-javascr...

http://davidwalsh.name/css-js-animation

http://www.sitepoint.com/incredibly-fast-ui-animation-using-...

http://www.smashingmagazine.com/2014/09/04/animating-without...

https://developers.google.com/web/fundamentals/look-and-feel...

For what it's worth, Velocity is a fairly new library. I wouldn't have gone down the path of JavaScript-based animation had my research and testing demonstrated that it was appreciably inferior in any way.

Re: on Saturday September 06, 2014 @08:13PM (#8279941)
Direct video link: https://www.youtube.com/watch?v=7IxhIMIdkPs&hd=1.

The ramifications of this plugin are significant for front-end developers. It saves countless hours of dev time by preventing constant IDE <--> browser switching and repeated UI state reconstructing.

Re:Ask HN: Books/Resources on Product Development? on Wednesday September 03, 2014 @03:24PM (#8264785)
One of my favorites is Lean Analytics. Goes over all aspects of product growth metrics.

Older »