Improving Angular performance with 1 line of code
1–10 of 118 posts
Re: Improving Angular performance with 1 line of code
#2Shouldn't debugging be something you opt-in to rather than opt-out of?
Seems like a weird design choice
Re: Improving Angular performance with 1 line of code
#3Shouldn't debugging be something you opt-in to rather than opt-out of? Seems like a weird design choice
> Seems like a weird design choice
Angular.js in a nutshell.
Re: Improving Angular performance with 1 line of code
#4Does Angular 2.0 make this one weird trick unnecessary?
Re: Improving Angular performance with 1 line of code
#5I'd like to see some data indicating there is actually an appreciable performance difference. Indeed, with only one line of code to add, the setup cost is low, but this article asserts a performance gain without any evidence.
Re: Improving Angular performance with 1 line of code
#6[deleted]
Re: Improving Angular performance with 1 line of code
#7Yeah this seems more like something that Angular should be doing, rather than the end user. If you're in a production environment Angular should enable this for you.
Re: Improving Angular performance with 1 line of code
#8I'd like to see some data indicating there is actually an appreciable performance difference. Indeed, with only one line of code to add, the setup cost is low, but this article asserts a performance gain without any evidence.
The official Angular docs describe it thusly:
You may want to disable this in production
for a significant performance boost
I'm inclined to believe the engineers who wrote the docs on this.
Re: Improving Angular performance with 1 line of code
#9Shouldn't debugging be something you opt-in to rather than opt-out of? Seems like a weird design choice
I'd be interested in how significant the actual performance hit is - I see no measurements.
There are plenty of times you'd want to enable various debug features, even in production, even if it means leaving them always on. The only real question is if the tradeoffs are worth it - the performance hit, if any, and the security implications, if any, versus the productivity gains.
Re: Improving Angular performance with 1 line of code
#10I'd like to see some data indicating there is actually an appreciable performance difference. Indeed, with only one line of code to add, the setup cost is low, but this article asserts a performance gain without any evidence.
The official Angular docs describe it thusly: You may want to disable this in production for a significant performance boost https://docs.angularjs.org/api/ng/provider/$compileProvider I'm inclined to believe the engineers who wrote the docs on this.
A Twitter engineer mentioned this in a lightning talk in the AngularJS SF meetup a little more than a year ago - he mentioned that he found speed gains of about 33% with that one line.
It's a great tool to have in your belt for optimizing angular apps, most people working with angular are not aware of this unfortunately.