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
Yes, Javascript is starting to get better and better. So all those frontend shit will get replaced by native Javascript modules so you can roll your own. Thats much better as Angular because you will have to accept the whole package. I dont understand why Microsoft developed Typescript because some Smart guys overthere did a lot with "dynamic" in C# and thats what Javascript is all about, checking at runtime and not at compile time. Microsoft is losing it. NodeJS will be the right replacement for ASP .NET if it can keep up with Javascript standards ES/6/7/8. May be Microsoft used it because they want to develop the whole web Mail program in it but thats not what "normal" developers use it for, its just wrong. Why is Typescript also wrong and those Microsot guys knows that, its the data you transmit across the line. Many times that data is very "dynamic" by nature. Just send and object with data and receive that object with data. No class description is needed and is just a lot of overhead. The more different data objects you will have the more Javascript will shine.