Does Angular 2.0 make this one weird trick unnecessary?
Improving Angular performance with 1 line of code
11–20 of 118 posts
Re: Improving Angular performance with 1 line of code
#12I'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.
Re: Improving Angular performance with 1 line of code
#13If you don't have a benchmark, you don't have a performance boost.
Re: Improving Angular performance with 1 line of code
#14Does Angular 2.0 make this one weird trick unnecessary?
http://i1.kym-cdn.com/photos/images/newsfeed/000/633/254/14f...
Re: Improving Angular performance with 1 line of code
#15Re: Improving Angular performance with 1 line of code
#16Shouldn'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
#17Re: Improving Angular performance with 1 line of code
#18Shouldn't debugging be something you opt-in to rather than opt-out of? Seems like a weird design choice
Django has DEBUG set to True by default, too.
Re: Improving Angular performance with 1 line of code
#19Slow websites hate him!
Re: Improving Angular performance with 1 line of code
#20Shouldn't debugging be something you opt-in to rather than opt-out of? Seems like a weird design choice