faux

Similar project: Capt - https://github.com/bnolan/capt by Ben Nolan ( Anyone remembers behaviors.js for Prototype way way before jQuery ? ) Also see: Faux - https://github.com/unspace/faux

I think it very much depends on what gets "abstracted away." If a library provides sensible defaults, or does some convention over configuration, it helps me ignore the inessential. And my knowledge is portable to other frameworks, I still understand the underlying model, I just don't have to mess with the details. In this we agree. But if a frameworks provides an abstraction that isn't isomorphic to the underlying model, I end up learning a non-portable technology that is useless when I step outside its cozy implementation. For example, ORMs that hide SQL from me. Messing with SQL syntax may be inessential, but working with actual relations is my job, and not knowing how to use a database is counter-productive. JM2C, YMMV, &c. p.s. I forgot to confess my own sins: https://github.com/unspace/faux

I obviously* like Backbone.js+jQuery, although colleagues are using Sproutcore on a "Rich Internet Application." I'm a big fan of applications that use the web model, so now that Backbone.js has added Controllers and History for route support, I give it five out of five stars. * http://github.com/unspace/faux

http://github.com/unspace/faux and: http://www.flickr.com/photos/thomasb/