While I decided not to use backbone, there is a need for a more structured encapsulation and abstraction of functionality. For example, if the architecture you

While I decided not to use backbone, there is a need for a more structured encapsulation and abstraction of functionality. For example, if the architecture you'd like to build only serves JSON and HTML templates, and javascript renders the rest, you save a lot on bandwith and cpu. The html is cached in the browser, the server only needs to produce JSON. Add a JSON based, restful DB, and you have an architecture that really fits what the web is becoming. The JSON layer is perfectly suited for being the API layer other clients as well - otherwise you might have a lot of crufty code on the server that has to be cleaned up for use by any other client (e.g. native iPhone). BTW - I believe the author of ligament also contributes to http://www.sproutcore.com/ http://www.sproutcore.com/ and jQuery