I disagree with the majority of this article. There seems to be a theme in there that angular is too heavy (Java, templates, performance, time reading DOM on l

I disagree with the majority of this article. There seems to be a theme in there that angular is too heavy (Java, templates, performance, time reading DOM on load) for the front-end. There's really a false premise at play here - that apps these days are as simple as they once were. Imagine for a second that front-end applications are vastly more complex than they once were (because they are). For any of us who have built more complex front end tools, you need something to help you manage the complexity you're now carrying around. Now the rest of it starts to make sense. More uptake from backend devs than front-end devs? The backend guys have built large complex systems in the past, they know that a tool like this can help them and it's something they're used to dealing with. Prescribed structure to your code? Yup, sounds good - I don't want to spend my day figuring out someone's callback spaghetti or DOM updating triggers from random locations. Front-end templates? If you don't need them and you're using angular you are using the wrong tool for the job.