My bet is when you get back to "basics", you will end up writing some ( probably worse ) rendition of views, models, collections, and events.
They are the most basic components of any good UI and if you find yourself deviating from them too much you're probably in the early stages of Dunning Kruger. My advice. God knows I learned the heard way. Develop a little humility and learn from the decades worth of history of people who came before us.
None of these application architecture problems are new. Backbone is simply the re-introduction of time tested historical principles to all you young amnesiacs.
> develop a little humility, all you young amnesiacs
Really? There's no need to be insulting or condescending.
The reaction against Backbone is that people like the tutorial author evangelize it as a universally better solution, like the line about the original example code: "It looks like most JavaScript code I wrote a year ago." That's just smug and annoying.
And while a strong MVC pattern is appropriate in some instances, the fact is that it is not appropriate for probably 95% of web apps out there. Instead, it's over-abstraction and over-architecture that gets in the way of productive development.
They are the most basic components of any good UI and if you find yourself deviating from them too much you're probably in the early stages of Dunning Kruger. My advice. God knows I learned the heard way. Develop a little humility and learn from the decades worth of history of people who came before us.
None of these application architecture problems are new. Backbone is simply the re-introduction of time tested historical principles to all you young amnesiacs.