BackboneJS is not the best option for MVC in the browser - Jeff Deville
1–4 of 4 posts
Re: BackboneJS is not the best option for MVC in the browser - Jeff Deville
#2We tried Knockout first. We encountered browser incompatibilities and performance issues that indicated an extremely alpha framework. We switched to Backbone and haven't looked back.
Re: BackboneJS is not the best option for MVC in the browser - Jeff Deville
#3Sigh, why do people always do a versus comparison with tools...?
Backbone like Knockout are tools. You choose the one that fits the job.
It's like comparing a hammer to a mallet. "Oh but the hammer is cast, and is sooo durable! Versatility at it's finest!" Until you notice that cast hammer doesn't work well on more delicate surfaces.
The beauty of backbone is it's just enough to get things done. Need more? Then go Knockout, by all means! But do not choose one tool just because it has more more more!
Just as in programming you choose to use switch/case, if/else, or do/while so should you decide on the macro lexical level of languages _and_ frameworks.
Sigh...
Re: BackboneJS is not the best option for MVC in the browser - Jeff Deville
#4Sigh, why do people always do a versus comparison with tools...? Backbone like Knockout are tools. You choose the one that fits the job. It's like comparing a hammer to a mallet. "Oh but the hammer is cast, and is sooo durable! Versatility at it's finest!" Until you notice that cast hammer doesn't work well on more delicate surfaces. The beauty of backbone is it's just enough to get things done. Need more? Then go Kn…
jjm - I tried to do a plus/minus on each piece of the framework. I think I agree w/ you in spirit. I'm even using bits of backbone in my finished project, just not all of it. With backbone seemingly getting the lions share of the press lately, I wanted to show that there are other frameworks, and while incomplete, they excel in some areas that backbone does not.