Backbone.js Was The Future

[@alegherix]

Really interesting video, amazing how much the Webbdev eco system has developed over such a relative short period of time.

[@charisginn3463]

starting a new job at a company that's converting from backbone to react. this was a great overview, thanks Harry!

[@joshr96]

Thanks for the trip down memory lane. I too started out with Backbone + jQuery. You got it 100% right with the View layer being Backbone's biggest flaw. I always thought it would be nice if you could just "re-render" your views, but like you pointed out that does not work with a simple template + insert HTML approach. Thankfully React came out and finally gave us that functional programing style view layer :)

[@ybtech]

What about backbone,marionette? I was surprised to see you leave that out. Great info. Thanks.

[@rick-says-hello-world]

The one thing that Backbone still did (does) better than any of the other major JS frameworks, was the ability to truly isolate your HTML from your JS. It took some discipline, but it was at least possible. Angular and many other frameworks add magic attributes into HTML, and React and others interleave HTML and code. But Backbone could be done where you had the opportunity to let a designer build or adjust your HTML and CSS without having to retain or reintroduce coding directives into it.

[@errinwright]

So with React can you still use event listeners? Or does react handle everything with the onClick?

[@abdella4]

Interesting. I'm interviewing for a front end react position and their application was created in backbone. This helped me understand why they're switching. Also their backend is rails so makes sense why they chose backbone for the frontend.

[@bryku]

MVC existed for a long time, but backbone was the first major framework that sort of did it for you... especially on the client side. Otherwise, most people were writing their own, so when backbone came out it gave us a standard to use, that made it much easier to work with teams.

[@pinatacolada7986]

Thanks. This was helpful.

[@djpunisha29]

what comes after React?

[@theyreMineralsMarie]

See Solid JS

[@djpunisha29]

@@theyreMineralsMarie Saw couple of videos, looks promising, thanks

[@teosurch]

Interesting, thanks for so cool historical video

[@muharief3885]

I 'm seeing this while i have successfully find a way to use ionic component with backbone. And its awesome. Well its marionette js actually that helped me a lot.

[@shrooobdude]

Still use backbone+marionette at my job 😂😂

[@greatscott8680]

Ditto.

[@suryaaravind3735]

Ditto

[@lonesomelacowboy]

thanks for sharing

[@simomed5002]

one day someone will create a similar video called "React was the future" and it seems that programmers don't want to get it, they keep themselves busy learning the frameworks and the latest features... same for typescript, back in the day I was writing coffeescript and I was thinking I am smart, until the time came when everyone started to move away from it and I had to rewrite all my code back to vanilla JS, people these days are writing typescript for similar reasons... some day they will get the lesson :)

[@djpunisha29]

Interesting, so many new tools and frameworks but still, everything is made on the same principles, there were no limitations to develop React back in 2010 ...

[@dev__adi]

Do Ember next 😇😇

[@JohnVandivier]

and angularjs came out a week later

[@borjinator]

On the oldest anarchy server in Minecraft…

[@IlhanNegis]

aaa goodoldays, knockout.js knocked my socks

[@spirobel]

I really enjoyed this video! Thanks! :-) More people should look at this and try building something with this. There are people out there that are still not sold on the idea of SPAs and hate on react. If you are not sold on SPA -> try to build something with backbone.js; if you are not sold on react -> try to build something with ember.js. Why are you omitting ember in favor of angular btw? ;-D

[@djpunisha29]

do AngularJS , spent some time with it, kinda miss it :)