With these other frameworks, which might be very large or very slow or very complicated, they enforce that design on you. For most projects, who cares? Use whatever is fun for you to use. Learn 'em all. But at a certain scale, it matters deeply what you hitch your wagon to.
How does Backbone relate to the points the original article makes? What are your comments?
I don't want to put a client ( I work as a freelancer ) in the position to look for someone that knows framework "A" or "B". Also I'm pretty sure "A" or "B" will soon be obsolete and the successor will need to change the whole codebase, instead of improving it.
I'm not talking about Ember, actually I'm also using it, but when it happens to go for scalable project I would prefer Backbone, because of team members learning curve and potential developers availability.
The issue with that is that the learning curve is now higher because the chances that a developer knows those missing parts that you added or coded is increasingly small.
Btw, I'm a heavy Backbone.js user so I still think it's a better option compared to other MVC flavours but I do have the problem that a lot of things related to data binding and UI animations is custom built and have the issue described above.
That's one of the reasons when I'm a part of a team and I need to make a decision about a framework, I usually go with Backbone. It's source code consists of one file that can be understood for less than an hour.
Last non-sense in this complexity is the boom of JavaScript framework specific languages that pop up. Like ReactJS and recently Angular 2.0 is preparing their own language for using it's platform.