I don't get it - why are people so interested in Backbone.js? It seems to impose the same kind of baggage in interfaces/front-ends that operating systems impose.
Lots of configuration, tons of conventions to learn, lots of little files... personally, in Javascript I create classes of things I want to draw, and they know how to draw themselves. Is that so bad? Now... granted, I don't build CRUD apps. I do visualization and data apps. But... it just seems like Backbone.js puts me in Java world in a browser.
While I absolutely share your confusion as to why this particular link sat towards the top of HN for so long, there are lots of reasons to be interested in Backbone.js.
Ideally, there is little to no configuration, a very minimal set of conventions imposed by the library (especially when compared with others in the space), and as many or as few files as you feel like using. But to be specific:
Backbone.js is a minimal implementation of the foundation that many MVC-ish JavaScript apps tend to acquire during their lifetimes. I would imagine that in many of your visualization/data apps, you have models of the data, and UI components that render the data and react to changes in the models. Backbone gives you convenience methods for those basic operations: binding events to changes in the data, granular re-rendering of UI components, map, reduce, filter, reject, serializing models to/from JSON ... and leaves the rest of it up to you.
backbone.js is made for CRUD apps. It's not surprising that a library designed for CRUD isn't immediately helpful in visualization. It may help you organize some of your data though.
Lots of configuration, tons of conventions to learn, lots of little files... personally, in Javascript I create classes of things I want to draw, and they know how to draw themselves. Is that so bad? Now... granted, I don't build CRUD apps. I do visualization and data apps. But... it just seems like Backbone.js puts me in Java world in a browser.
Am I wrong? Why? How does backbone.js help you?