[igl]

Not trying to be cynical, but i am kinda glad that backbone is "over" for me. Been with it for about 5 years or more and i have seen big projects fall apart. You don't see the tree behind all the leafs after a year of coding.

With flux/react/angular around development is a lot more fun again. I can't imagine going back.

[bryanlarsen]

In my personal experience, backbone has held up better than angular 1 has. Completely different projects and teams so it's hard to draw conclusions.

React + flux implementation du jour looks really promising, though.

[enraged_camel]

What is interesting to me is that the top comment at the time I write this provides the opposite anecdote, that they have seen huge projects using Backbone go really well.

Makes me wonder if there's some sort of objective comparison and analysis of frameworks, or if everything is based on anecdote and personal experiences.

[igl]

Success mostly depends on the size of the team and their culture. Do they do code reviews? Refactor early and often? Is there a architecture plan that is enforced and trained to new hires?

Frameworks do give you a corset to work within. I do not claim backbone wasn't a success. Just providing that was big.

[feedjoelpie]

While I have largely moved away from Backbone, what makes Backbone really great, still, is its adaptability. While I wouldn't endeavor to write a brand new application with it so much anymore, it's extremely hackable and especially great for abstracting away ugly legacy web service APIs. It's definitely saved my sanity on that front on more than one occasion.