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

Try webrocketx Vlad. Full disclosure. I wrote it. It’s a nice way to turn a classic web application into a SPA, greatly reducing the amount of server side controller logic you need and also making the application band width lower. From: Vladimir ***@***.*** Sent: Monday, September 13, 2021 9:32 AM To: tdd Cc: matthewekeller; Comment Subject: Re: tdd/angular-just-say-no.md @VladimirtheGreatest commented on this gist.

…

_____ I can confirm that angular is trash for me. Documentation is terrible, no good examples. If you want to simply change some values in your forms it takes so much effort, even if you search on stackoverflow most of the best answers are marked as "this is a bad practice for angular". I dont really understand what is the point of all that rubbish but for simple project that requires some crap CRUD operations + dom manipulations jQuery serves the purpose. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://gist.github.com/5ba48ba5a2a179f2d0fa#gistcomment-3891583> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANE5574POAUEKE6B6XK7ARLUBYRQFANCNFSM4HKYW5CQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> . Image removed by sender.

Mat I will look into it may be its something but for now I believe changing the a tags and form tags in Ajax calls does the trick for me. I use the history to push/pop parts of the screen.

I'm so sorry, i missed the 9th of July mark this year.

Is Angular dead yet ?

Hopefully soon. Ha ha From: Shireilia ***@***.*** Sent: Tuesday, September 14, 2021 7:22 AM To: tdd Cc: matthewekeller; Comment Subject: Re: tdd/angular-just-say-no.md @Shireilia commented on this gist.

…

_____ I'm so sorry, i missed the 9th of July mark this year. Is Angular dead yet ? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://gist.github.com/5ba48ba5a2a179f2d0fa#gistcomment-3892745> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANE557ZVRS5S3AD3LFSBI43UB5K7HANCNFSM4HKYW5CQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> . Image removed by sender.

Angular is just conceptually wrong! You are compiling stuff for interpreter!

It's like using diesel to power electric car...

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.

[1] I dont understand why Microsoft developed Typescript [2] because some Smart guys overthere did a lot with "dynamic" in C# and [3] thats what Javascript is all about, checking at runtime and not at compile time. [4] Microsoft is losing it. [5] NodeJS will be the right replacement for .NET if it can keep up with Javascript standards ES/6/7/8.

So:

1. [3] is the answer to [1].
2. [5] is wrong for various reasons, including [3].
3. [4] is probably correct, but has nothing to do with Javascript, Typescript, or C#.
4. [2] doesn't seem very related to either [1] or [3]... I suppose it could be a justification for [4], but that doesn't really make sense in light of claim [5]...

@VladimirtheGreatest jQuery was great but its not needed anymore. Javascript can do now what jQuery can do. Not all plugins are available as Javascript modules. Thats the price you have to pay. But the reward without jQuery will make up for it. As I have said before ES6/6/7/8/etc is the way to go.

@obeobe I do NodeJS and ASP MVC .NET at high level. Did also study Microsoft CMS Orchard. Those guys did a lot to make the ASP MVC .NET backend work "dynamic" with the Javascript frontend. With NodeJS Orchard CMS would be developed much easier because its dynamic by nature. But is just my thoughts about it. Did adjust my post, NodeJS will replace ASP .NET, not the Desktop .NET. I still see use for that. Its easier for a dynamic frontend to communicate with a dynamic backend. The Typescript idea is the other way around. And I do disagree with that and Microsoft did prove did themself with Orchard CMS.

@hhvdblom But C# is not just ASP MVC .NET or Orchard...

Anyway, I use both C# and NodeJS. I think both are impressive technologies / ecosystems.
I also dislike Angular, though I don't think its conceptually wrong.
But Typescript... I find Typescript indispensable when working on large systems and targeting JS...

@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.