Backbone vs. Simple JavaScript Inheritance

Post by asuth » Sun, Jun 02, 2013, 1:49 AM UTC

recroad wrote: post #19

asuth wrote: post #3

For our recently launched flashcards tool, we built it in Backbone. Demo: http://quizlet.com/23770911/flashcards Our experience was that backbone was very helpful in laying out code and providing clean event triggering, but that a lot of it was simply too slow to use. We started out with a View per card, but that was impossibly slow with 100+ cards (and we need to support ~1000+). We ended up with just one view for t…

Were you using Marionette? It helped me increase performance a lot by cleaning up views properly and organize their rendering optimally. I almost can't imagine using Backbone without Marionette.

Post by fizzbuzzd » Sun, Jun 02, 2013, 5:11 AM UTC

msoad wrote: post #8

Web developer spend too much time worrying about JavaScript performance I think. When one method can iterate around 100000 element in a second and the other 120000 elements, I would choose one that I am more comfortable with not the faster.

Post by toonketels » Sun, Jun 02, 2013, 8:54 AM UTC

AdrianRossouw wrote: post #22

recroad wrote: post #19

Earlier quoted context omitted.

Were you using Marionette? It helped me increase performance a lot by cleaning up views properly and organize their rendering optimally. I almost can't imagine using Backbone without Marionette.

I agree with you about not being able to get by without using marionette any more. The funny thing is, that I had to build something without it, to understand why I wanted it in the first place.