purpleturtle
A ‘memory foam’ approach to machine learning could reboot AI
Twitter releases a React plugin for Velocity.js
ZeroCater Says 20 of Its Small Partners Have Done More Than $1M in Revenues
This is an odd statement since I know there are at least two direct competitors who are far larger.
How Webflow got into Y Combinator
Founder stories: Webflow's Y Combinator journey [video]
Libscore v2: View the growth/decline of open source libraries and SaaS
How to deal with startup competition
How to deal with startup competition
Webflow's YC acceptance story [video]
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.
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.
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.
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 :)
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...
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.
Stripe: What the Open Source Grant was like
Show HN: Design UI animations in real time then export them to code
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.