21–30 of 90 posts
Excited to see the bind once expression introduce.
Yes, this is a big deal for performance! Having to run through 1000s of watchers in a digest cycle is not unusual with a typical Angular site and oftentimes most of those watchers are redundant.
Exciting to see, Angular JS is what is allowing my small team to create some pretty complex backend :)
> One-time bindings – by prefixing an expression with "::", it will only be interpolated once, and then no longer watched. Does anyone else find the DSL(s) in Angular to be maddening?
The DSLs would be okay to work with if they were better documented and had better examples and an easy to use docs system.
> And as we announced back in December, AngularJS 1.3.0 no longer supports IE8. This allowed us to make improvements and performance enhancements that otherwise would not be possible. It is possible, see how rivetsjs did that years ago. But it is still a very nice thing to drop IE8.
If Microsoft no longer supports IE8, why should web developers?
> One-time bindings – by prefixing an expression with "::", it will only be interpolated once, and then no longer watched. Does anyone else find the DSL(s) in Angular to be maddening?
The biggest mistake they've made with Angular is that they're using a custom documentation system that's also written in Angular and JavaScript. The DSLs would be okay to work with if they were better documented and had better examples and an easy to use docs system.
> One-time bindings – by prefixing an expression with "::", it will only be interpolated once, and then no longer watched. Does anyone else find the DSL(s) in Angular to be maddening?
That said, I too find the documentation too brief, especially on things like ng-repeat's filters.
Earlier quoted context omitted.
Yes, this is a big deal for performance! Having to run through 1000s of watchers in a digest cycle is not unusual with a typical Angular site and oftentimes most of those watchers are redundant.
Are there any benchmark results available? They mention it increased speed, by a lot, but don't give any numbers -- instead point to a code repo where you can run your own. This is great, but I want an "at a glance" numbers on a variety of platforms so I can verify their claim and then take it to my boss to push through an upgrade. An "executive summary" if you will.