Sorry for not clarifying.
Sorry for not clarifying. What I find awkward about it is the Angular-specific baggage and the syntax, which just got more complex. Stuff like ng-model-options="{ updateOn: 'blur' }" is far from straightforward. I guess you could do ng-model-options="model.modelOptions" and define the behavior in the controller, but then your controller would be handling far more than it should. By the way, wouldn't a separate directive be more appropriate for this? ng-update-on="blur" is more palatable. And in my experience with Angular, it's never just "assign a value to a scope and done", except for the most trivial situations. When you leave these behind, you have to think about scope hierarchies. You have to watch your watchers. When you use something like angular-translate, you have to carefully consider synchronicity issues and the performance drawbacks of each way to bind your models. And so on. I love the power and flexibility that Angular gives you, but I wish there was a simpler way for it to do its magic.
Posted by rmsaksida on Oct 14, 2014, 1:32 PM
Tags
Related issues
- Unless it is running on a government issued iPhone, it is not the Individual #1 you are alluding to.
- Great job, will try it.
- I also have a 2014 CR-V and I hate this too.
- I wish there was a setting to make audio and video opt in per site.
- There sure are.
- I feel like it's once a week that HN surfaces some incredibly overhyped, low-on-the-hierarchy-of-evidence ( https://en.wikipedi...
Raise real-world problems, find people facing the same issue, and discuss solutions.9,000 issues0 comments
complaint (Other)
Unless it is running on a government issued iPhone, it is not the Individual #1 you are alluding to.
NewGreat job, will try it.
NewI also have a 2014 CR-V and I hate this too.
NewI wish there was a setting to make audio and video opt in per site.
There sure are.
I feel like it's once a week that HN surfaces some incredibly overhyped, low-on-the-hierarchy-of-evidence ( https://en.wikipedi...
That usually works well enough for risc code.
> The Bulletin calls her Miss Swindell.
Sorry for not clarifying.
Sorry for not clarifying. What I find awkward about it is the Angular-specific baggage and the syntax, which just got more complex. Stuff like ng-model-options="{ updateOn: 'blur' }" is far from straightforward. I guess you could do ng-model-options="model.modelOptions" and define the behavior in the controller, but then your controller would be handling far more than it should. By the way, wouldn't a separate directive be more appropriate for this? ng-update-on="blur" is more palatable. And in my experience with Angular, it's never just "assign a value to a scope and done", except for the most trivial situations. When you leave these behind, you have to think about scope hierarchies. You have to watch your watchers. When you use something like angular-translate, you have to carefully consider synchronicity issues and the performance drawbacks of each way to bind your models. And so on. I love the power and flexibility that Angular gives you, but I wish there was a simpler way for it to do its magic.
Comments (0)
No comments yet. Start the discussion.