Angular: Just Say No

angular-just-say-no.md

Angular: Just say no

A collection of articles by AngularJS veterans, sometimes even core committers, that explain in detail what's wrong with Angular 1.x, how Angular 2 isn't the future, and why you should avoid the entire thing at all costs unless you want to spend the next few years in hell.

Reason for this: I'm getting tired of having to explain to everyone, chief of which all the indiscriminate Google Kool-Aid™ drinkers, why I have never believed in Angular, why I think it'll publicly fail pretty soon now (a couple years), and why it's a dead end IMO. This gist serves as a quick target I can point people to in order not to have to parrot / compile the core of the articles below everytime. Their compounded reading pretty much captures 99% of my view on the topic.

This page is accessible through http://bit.ly/angular-just-say-no and http://bit.ly/angularjustsayno, btw.

• I won't be using Angular for my next project...and neither should you. • Robert Greylin, Feb 2015
• The reason AngularJS will fail • George Butiri, Mar 2014 – Apr 2015
• Introducing Aurelia • Rob Eisenberg, Jan 26 2015
• Why you should not use Angular • Egor Koshelko, Jan 2 2015
• The problem with Angular • PPK, Jan-Mar 2015
• AngularJS: the bad bits • Mircea Moise, Sep 13 2014
• You have ruined JavaScript • Rob Ashton, Apr 23 2014

@obeobe Yes you have to do it like that. You must make an static object in Typescript. Send that to the server. On the server create a static object for receiving. Do that with say 300 objects and that will make your life easier? With Javascript send a dynamic object to the server and receive a dynamic object in NodeJS. The Node JS solution just makes more sense. And thats why I use it now. Combine it with MongoDB and yes we have a winner. By the way I was a big Microsoft fan, but times change, make way for the new King NodeJS.

@hhvdblom I guess that you are describing some Orchard-specific workflow. I can't address that because I have never even heard of Orchard until 39 minutes ago :) but it doesn't sound at all like how I work with Typescript...

@obeobe The guys that developed Orchard CMS had to find a way to handle Javascript objects that come in on the Server. Javascript object are dynamic by nature, even the Typescript ones after transpiling. They put in Orchard CMS a self developed dynamic C# component that can handle them. Problem was just to be simple: dynamic vs static. With NodeJS you do not have this problem. NodesJS is not perfect it needs to go along with ES standards but both sides are dynamic.

6 years later, Angular still not dead

I'll go with a classic :

Is Angular dead yet ?

Angular would have been dead if it wasn't for Google's infinite resources. The number of people using it are dropping like flies though.

Angular will be replaced. Thats for sure. Technologies like html-over-the-wire seems promissing. Htmx and Hyperscript are brand new. Let see what that brings. They are developed by guys that know Angular etc and are not happy with it.

Angular would have been dead if it wasn't for Google's infinite resources. The number of people using it are dropping like flies though.

Source ?

Woopsies, missed the 9th of July again.

IS IT DEAD YET ?

Angular is alive and well thriving with powerful new features in the recent v15 release.