Developing Backbone.js Applications – a Creative Commons book
addyosmani.github.io
Developing Backbone.js Applications – a Creative Commons book
1–10 of 22 posts
Re: Developing Backbone.js Applications – a Creative Commons book
#2no offense, but I am the only one who thinks this MVC style isn't an option anymore after things like react?
Re: Developing Backbone.js Applications – a Creative Commons book
#3no offense, but I am the only one who thinks this MVC style isn't an option anymore after things like react?
Er, adding an option doesn't delete all the other options.
MVC is a decades old, tried and tested pattern for building user interfaces. Whatever its merits, I suspect it will survive react.
Re: Developing Backbone.js Applications – a Creative Commons book
#4Interesting issue with discussion regarding ES6:
https://github.com/jashkenas/backbone/issues/3560
Re: Developing Backbone.js Applications – a Creative Commons book
#5Not 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.
Re: Developing Backbone.js Applications – a Creative Commons book
#6no offense, but I am the only one who thinks this MVC style isn't an option anymore after things like react?
Er, adding an option doesn't delete all the other options. MVC is a decades old, tried and tested pattern for building user interfaces. Whatever its merits, I suspect it will survive react.
This is not a critique of MVC, but rather the particular implementation that Backbone provides. With React you still have your models (and controllers).
And adding a new option may make an existing one obsolete. Remember ES3? I do, but I wouldn't want to write new code in it. Once new options were added (ES5, and then ES6), they made the old one obsolete. It desn't mean you can't use the old options, but why would you if the new ones are superior?
Re: Developing Backbone.js Applications – a Creative Commons book
#7no offense, but I am the only one who thinks this MVC style isn't an option anymore after things like react?
Well, "things like react" are not more than the V in your MVC ;)
Re: Developing Backbone.js Applications – a Creative Commons book
#8If we're just going to be Slashdot style anecdotal and start slinging... I've seen huge projects go really well in Backbone. I can't imagine going back to Angular.
Since when is 'fun' the bar for frameworks?
Re: Developing Backbone.js Applications – a Creative Commons book
#9no offense, but I am the only one who thinks this MVC style isn't an option anymore after things like react?
this book is old. It was written before React. I even do not understand why it is so high voted here. But many thanks for Addy writing it and making it open!!!
Re: Developing Backbone.js Applications – a Creative Commons book
#10Not 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.
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.