> The disclaimer clearly shows you realize they have different purposes. So why the antagonistic tone? As stated in the disclaimer itself; because people use b

> The disclaimer clearly shows you realize they have different purposes. So why the antagonistic tone? As stated in the disclaimer itself; because people use backbone as if it will help them manage the complexities of creating rich client side UI, when I actually think it's a terrible choice for that. > If your issue is really as stated that people use Backbone for the wrong things and to highlight the benefits of data binding for views, then address that, instead of writing some inane comparison blasting Backbone for not providing features you the at the end admit isn't its focus. I want to grab people's attention that they're doing it wrong. It's like when you slap someone in the face to wake them up. > It's a bit as if I were to review your blog post as musical theatre and then at the end admit I knew all along it was actually a technical blog post but that I'd decided to slate it for lack of singing anyway. Well, you're evaluating my article as if it was meant to be an objective non-biased review of "pros and cons". It's not. It's an opinionated piece of text that comes from personal frustrations. Though for the record, I actually respect and admire the author of backbone, after all, he's also the author of coffee-script, which is just awesome.