4 ms·
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." vie
by lars 11y ago
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.
- smokeyj 11y ago> after having spent over a year working with it on a large project What issues are you running into? I always hear people complain about angular but rarely hear why.
- julie1 11y agoMost people don't understand directives, so they resort to a pub/sub communication model that makes the web page unable to scale when you have too much items that are binded/coupled on a page. No optimizations are possible for an exponentially resource greedy problem.
- lars 11y agoI just linked my multi page blog post describing the problems I ran into.
- ralfn 11y ago> The decision to have scopes be objects that (sometimes, not always) inherit from one another, is entirely on Angular It's almost as if they try to shoehorn a custom adhoc programming language straight into your dom-nodes, but they couldn't be that stupid, right?