3 ms·
Totally agreed about yearning for a directory of JavaScript frameworks. I use a little jQuery, and I'm getting to the point where I'm ready to add a little mor
by socratic 15y ago
Totally agreed about yearning for a directory of JavaScript frameworks.
I use a little jQuery, and I'm getting to the point where I'm ready to add a little more structure. But should I be using Backbone.js? Spine claims to be cleaner, but how do the communities/plug-ins compare? How does KnockoutJS compare? BatmanJS? Should I be abandoning jQuery for something more extensive like SproutCore or Sencha?
I'm also totally unclear on how compatible things are. A lot of the frameworks don't even seem to agree on basic things like how to do inheritance or whether they should use JavaScript or CoffeeScript. (Though I suppose they mostly don't break each others' namespaces any more.)
Is there some over-arching list of features that covers all of the existing frameworks, and that could be put into a table? If so, does such a table exist? If things are just a popularity contest, who is winning the popularity contest?
- jashkenas 15y agoYou should dig around, ignore claims of cleanliness or ease of use, read a little source code, and see which one floats your boat. One way to get a good idea about how useful these frameworks are in practice is what's being built with them. (I work on Backbone.js) You can take a look at the sort of apps folks are coming up with by scrolling through here: http://documentcloud.github.com/backbone/#examples http://documentcloud.github.com/backbone/#examples ... keeping in mind that Backbone hasn't even been out in the wild for a year yet, at this point.
- derrickreimer 15y agoThere is a pretty nice list of JS libraries here: http://www.everyjs.com/ http://www.everyjs.com/