I got tons of both hate and love for that blog post. One of the few criticisms that I can accept is the "The problems are real, but don't matter that much." view. I don't agree, but I suppose people can have different experiences there.

Any 'sensationalism' comes from legitimate anger with the framework, after having spent over a year working with it on a large project.

> Now your point about ng-model and scopes is valid.But it's not a angular problem, it's a javascript issue.

This I don't agree with. Yes, JavaScript has prototypical inheritance between objects, but certainly not between scopes. It has lexical scoping like everyone else. The decision to have scopes be objects that (sometimes, not always) inherit from one another, is entirely on Angular. So is the decision to have ng-model silently create objects on this scope.