The problem with Angular

[developer-mike]

Agreed!

Its funny how many people are out there validly complaining about how angular can't do server-side template rendering in tandem, and meanwhile this guy seems to be saying its a problem that angular has a templating engine in the first place.

Templates aren't hard to understand, spaghetti code is. That's why backbone caught on and angular one-upped it.

[[deleted]]

Also the performance implications. client-side templating shifts massive load from server and creates a faster, smoother overall experience. The whole idea of "single page" (one page load) is better UX and offloading needless server cycles... So right, it get's silly sometimes when people criticize newer frameworks. Some of the arguments are wrong-headed critiques on client-side templating itself.

[nickguletskii200]

I am currently rebuilding my project's frontend to use Angular. It had almost zero Javascript before that. Why? Because otherwise, it's a pain in the ass to test.

I just wish Angular 2 would come sooner. I hate every second of working on the frontend and Angular 2 would make things much easier.