When I read this article pointing out supposed problems with the AngularJS framework, I was hoping for some points on whether Angular fulfills those needs of abstraction and maintainability, correctly balanced with its flexibility and ease of use. As far as I can tell however, the author dismisses Angular as a framework that appeals to Java developers, while insisting that front-enders have developed their own coding styles and are thus resisting the Angular Way ™. Throw in a few well-publicized performance shortfalls, and it’s easy to dismiss the framework as lacking.
Fallacies aside, the article did make me step back to identify this so-called “front-end coding style.”
None of these scenarios, however, exclude the legitimate need for the standardization and modeling of code in complex web applications. Forgoing frameworks for the sake of simple functionality should be a measured engineering tradeoff, not a refusal to understand the underlying principles.
- I’m only half-joking; I have interviewed a handful of folks who proudly show off their portfolio of sites built on top of their own creations. It’s serviceable as a learning exercise, but not as a showcase of good engineering practice.↑
- Though not a JS framework per se, Google Web Toolkit (GWT) focused on abstracting away the browser client at such a high level that even just getting to the DOM was an unpleasant experience.↑
- Despite the accusation that Gmail and Google Plus don’t use Angular – they’re giant apps that were written way before the framework was even conceived – the style they’re written in, with the Closure library, resembles Java code and embodies many of the same best practices.↑