> What Backbone offers is a light layer of structure over your code.
It is strange to me implement a design pattern as concrete code. It's like implementing MVC pattern as "Model" "View" and "Controller" classes and forcing everyone using MVC to use your code package. Design patterns are knowledge and are not in 1:1 relation with code.
I kind of think of backbone.js as a set of patterns to write your code in, but then someone went in and abstracted the common pieces out so you don't have to reinvent the wheel.
A simple example is the Backbone Events module. Sure, you could wire up your own event handling code, but why would you want to? Using a common library like backbone means that all of the bugs are fixed in a common place and you don't have to worry about it.
It is strange to me implement a design pattern as concrete code. It's like implementing MVC pattern as "Model" "View" and "Controller" classes and forcing everyone using MVC to use your code package. Design patterns are knowledge and are not in 1:1 relation with code.