> This persistent idea that one should compile templates on the server is so mindbogglingly inefficient - compared to delegating to clients whose computing power is idling 99% of the time.
s/idling/conserving battery life/
much of the original article's criticism was aimed at angular apps on mobile devices.
Re:The problem with Angular
by JustSomeNobody on Wednesday January 14, 2015 @11:45AM
(#8887336)
Hi. So you're responsible for the increased battery usage on my mobile device. Please stop. Also, can you please test your code on a device that came out _last_ year? You know, so that you can make sure it's not sluggish and frustrating to use.
I would have thought a page reload from the server would use much more battery than a simple digest/apply in Angular.
Re:The problem with Angular
by polynomial on Wednesday January 14, 2015 @02:46PM
(#8888543)
Is there an Angular engineer who can speak to this?
This persistent idea that one should compile templates on the server is so mindbogglingly inefficient - compared to delegating to clients whose computing power is idling 99% of the time. Not to mention separation of UI from the core functionality and other benefits.
JS in browsers is incredibly fast nowadays. I can't remember the last time I ran into performance issues. Angular my not be the most efficient but it's a stepping stone in the direction of client-side apps + RESTful APIs which I think will be the rule rather than exception in the future.
Lots of features are in the pipeline which will make client-side apps even faster and more elegant (shadow DOM, Object.observer).