News for hackers. Stuff that matters.
Re:The problem with Angular by 3princip on Wednesday January 14, 2015 @11:10AM (#8887109)
This is basically a +1 reply but I feel strongly about this point and wish to add my own rant.

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).

Re:The problem with Angular by philsnow on Wednesday January 14, 2015 @11:21AM (#8887196)
> 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.
Re:The problem with Angular by joewood on Wednesday January 14, 2015 @12:14PM (#8887552)
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?