This article is mostly BS. He's got the knack of sounding like he knows what he's talking about when he actually doesn't. Some examples: "Angular’s ng-repeat d

This article is mostly BS. He's got the knack of sounding like he knows what he's talking about when he actually doesn't. Some examples: "Angular’s ng-repeat directive will create or destroy DOM elements accordingly. This turned out to be quite expensive. ... ... what worries me is that this non-performant mode is Angular's default. Front-end framework defaults should use established front-end best practices. Angular’s don’t." He's talking about ngRepeat's "track by" function here and clearly doesn't understand that it can't be switched on by default as the user must specify the name of a unique id used in their data models. There is no way for this to be on by default. "Although templating is the correct solution, doing it in the browser is fundamentally wrong. The cost of application maintenance should not be offloaded onto all their users’s browsers (we’re talking millions of hits per month here) — especially not the mobile ones. This job belongs on the server." What does that even mean. Consumer hardware contains heaps of resource for web browsing. "Many front-enders, on the other hand, who have worked with JavaScript and browsers for years and have developed their own coding style" Cute front-enders with their own adorable coding styles. Code is code. Patterns structure code to increase maintainability. Stop imagining there's a group of people whose work this does not apply to. "That’s why most Angular developers come from the back-end, particularly from Java. As far as I know this situation where a front-end framework is supported mostly by non-front-enders is unique." More of this front-end/back-end discrimination bullshit. That's a distinctly enterprise paradigm that just has to go. It's 2015