Member-only story
Part Of Why I Think Angular Is Junk

Several years ago I wrote about how I think React is junk. The article proved popular and led to a few follow-up's. My recent “Bad Examples” article got me thinking back to that, and how I really dislike all of these scripting frameworks. So I figured it’s been at least a couple years, let’s put something else in the crosshairs.
To me, systems like Angular are hard to learn, way more work, and generally are used for things I would NEVER use client side scripting for in the first damned place. The claims of merit ring false, and in the handful of cases I would do things with client side scripting I can and would do so in a fraction the code letting HTML and CSS do the heavy lifting, and skipping a lot of the “proactive paradigm” career educator bullshit bingo that just makes everyone work harder, not smarter.
And that brings us to the first majorstrike against it:
1 : It’s Usually Used “Client Side Rendering “ (CSR) Only!
Whilst there are plenty of scenarios where CSR is warranted, for the most part every time I see Angular in use it’s on websites where it ends up an accessibility violation. Users (or their employers) oft disable scripting for various reasons and/or creates issues. For example:
- Just plain distrust. This is common for employees…