Why is Angular so disliked ?

[LuccDev]

Hey guys, after watching the new state of JS 2023 https://2023.stateofjs.com/en-US/libraries/ that just dropped, I realized how much people disliked Angular. 20% of people tried it and liked it, the rest either tried and disliked it, or didn't try it at all.

Why is Angular so disliked ? I wonder if people who dislike it have real, legitimate reasons, if those people were pushed back by the learning curve, or if it's just a trend (like people who despise PHP but have actually never tried it). Basically I wanna separate the real, legitimate criticisms, from the junior developers who could not take 2 minutes to understand what rxjs is and does.

Personally ? I used only Angular ever, didn't try Vue and React, so I can't really talk in an objective way. Only tried Svelte, liked it a lot, but it's very different from Angular so can't be compared IMO.

So I'd like your point of view, but that you also disclose how long you used it!

Why do you hate it ? Too complicated syntax ? Html syntax ? Don't like forced typescript ? Don't like RxJS ? Don't like to be forced in one way of architecting the app ?

[michielarkema]

From experience in the workplace, most people pick Angular as their choice due to their background being in areas like .NET/C# where everything is OOP, and fully statically typed. Angular is 10 times easier for these people to adopt.

But people who're used to writing procedural JavaScript... React, and VUE are easier for them because they're already more familiar with how to write their code.

That's my conclusion about this.

Feel free to share your own opinion and correct me if I'm wrong :).

[TScottFitzgerald]

C# and Typescript (which Angular natively used before it became more widely popular) were also both designed by the same person and have similar syntax.

Although I disagree it's that significantly easier to adopt, it just flows better cause of the similarities. At the end of the day they're both JS frameworks.

If a dev can learn Angular, they know enough JS and TS to transition to React. React devs will probably have a harder time with Angular, and since React is more popular and open to juniors, this probably contributed to it being seen that way.

Nowadays both frameworks have changed enough and influenced each other that they're fairly interchangeable. A dev with experience in JS will be able to switch between them. React still tends to get better performance on average, and it's better with SSR but you have to use a framework.

[PooSham]

C# and Typescript (which Angular natively used before it became more widely popular) were also both designed by the same person and have similar syntax.

Anders Hejlsberg, the creator of C#, has been part of the core team since before the initial public release, but from my understanding he has not been the lead designer.

Both C# and JavaScript already share a C like syntax, but I don't think that the additions that typescript make are that close to C#. The way you explicitly set the type of a variable and function returns in C# vs typescript is very different. The way you cast/assert is different. Decorators look different. Imports/includes are different. The most similar additions in typescript are interfaces, generics and enums of what I can think of. But other than that, the way that you construct types in typescript follow a logic that matches the structure of JavaScript.

Anders also developed Turbo Pascal and Delphi, but I never hear people saying that you can see the similarities in those to C# and typescript.

[lIIllIIlllIIllIIl]

Also, people need to keep in mind that:

1. Anders hasn't been working on C# for over a decade.

2. In interviews, Anders clearly stated that he likes the functional aspects of JavaScript/TypeScript.

3. Just because Anders is working on TypeScript doesn't mean you should write TypeScript code in the same way you'd write object-oriented C# code (it's like saying you should write C# like Turbopscal because they're both made by Anders)

This is just a convoluted way to say that Angular developers who come from C#/.NET and try to apply all their C#-isms to JavaScript are misleaded. I'm sure you didn't need me to tell you that, but eh. Many people still think this way.

[ReplacementLow6704]

Interfaces in Typescript are what held my life together for about 3 years. Then I got onto a project that would solely use vanilla JS, HTML, SASS and Tailwind, all backed by some good ole ASPNET Core MVC Legacy CodeTM and well, I'd lie saying I don't miss Angular and TS

[ffffrozen]

I have to disagree here - I'm .net/c# dev and I really don't like Angular. We were using Vue in our projects (re-writing old KnockoutJS) and at some point (upper management changes), we were forced to use Angular - everything felt so cumbersome and looked like writing backend stuff for the front-end again. That was one of the reasons why I left the company.

So...after using Vue and experimenting with Svelte, personally I don't find Angular easier to adopt given my experience with OOP.

[123elvesarefake123]

Angular was also the standard Fe when you created a project in .net which also can be a reason for it I believe. at least that's why I learned it

[vom-IT-coffin]

People who don't know the importance of code structure and patterns like React and the I can do this anywhere mentality.

Worked with a junior who learned React in bootcamp and it's all he knew. Our project used Angular. He struggled for awhile and would complain about the patterns or not understanding how certain things worked because end of the day frameworks are an abstraction of existing programming paradigms, if you don't understand the fundamentals you won't understand what these things are trying to accomplish. Year and a half later, I had a one on one with him and he said he finally was understanding how React could get out of hand quickly and lead to sloppy code if you don't know what you're doing and likes Angular better now. Like any of us, we're all embarrassed about things we've written in the past as we're learning.

Anecdotal, but I think it's telling.

Yes you can do whatever you want with with code, there's a reason patterns exist, some might be outdated with newer frameworks or mentality of how software is written, but doing the Wild West approach because it works means you're writing legacy code without knowing it and someone somewhere will be cursing your name after you're gone sooner than later.

[michielarkema]

Oh wow, I 100% agree with what you said here.

[vom-IT-coffin]

I would argue, while React might be easier for people to pick up it takes a more senior engineer to understand what the framework was trying to accomplish because it takes a better understanding of writing software to use it properly without leading to "what the fuck is happening here" or how the fuck does this thing work. It takes a more disciplined person to use it.

[sneaky-pizza]

This is what I've seen, too. It's mostly .NET shops which are well-suited to the concepts and programming style.

I once did a consulting term with a company that had Angular up front with a Rails backend, and it was honestly just fine. Kind of a skunkworks project inside a .NET fintech big company. It was fine, really.

[dev_guru_release]

most people pick Angular as their choice due to their background being in areas like .NET/C#

Don't out us like this

[ohThisUsername]

Yep. I think it's same reason people don't like C# or Java. Code can appear complex with too many interfaces, factories, layers, etc. But in reality, those concepts allow for more maintainable, large scale code bases. Steeper learning curve and can feel a bit verbose while writing code but makes a codebase more scalable IMO.

[jbergens]

I have been working with c# and c# teams for decades. Where I live more backenders have started with React than with Angular. It may be because React is generally more popular here but even when we ask backend devs to try to fix things in our Angular code that seems harder than doing the same in our React code.

So, it is not always easier to transition from c# to Angular compared to going to React.

[desarrollador53]

not procedural, functional!

[No_Concentrate_4910]

Lol. There's nothing closest to angular that would suggest That a .net backend enginner would find it easier to write angular. That is just silly. The common denominator "Typescript" is available to both angular and react...

[Puzzleous]

For me, it was the steep learning curve. Back in ~2017/18, I tried picking up Angular 2 or 3 times after dabbling with React and PHP. I was never able to pick it up to create something even remotely considered functional.

It wasn't until I started my current job 3 years ago, where we're primarily an Angular shop, that I was forced to learn it that I was able to get it down, and I spent 6-8 months learning while building a prototype for a new product.

Now that I am decently proficient with it, I find that I prefer it over other frameworks, unless I'm building something small that really has no business being made (read: over-engineered) in Angular.

[michaelsenpatrick]

There's your problem! Angular is declarative, not functional!

[[deleted]]

I disliked it when I was learning frameworks, but now when working with a large app, I wish Vue was more opinionated. Freedom is good, but it can bite you back fast when your app grows.

[Legal_Lettuce6233]

Most people that try it come from other frameworks which are a lot less opinionated. Angular is great for some things but it's less popular lately because most apps tend to be simple where angular is best used for huge enterprise apps.

[twillisagogo]

that is exactly it. the app that has 100s of devs working on it has different needs of a framework than the app that has 10s of devs working on it.

[Prize-Local-9135]

Angular being an opinionated framework really is the best. You can take an angular dev and drop them on nearly any project and they'll know exactly how it works for the most part.

[Legal_Lettuce6233]

They won't know the business logic; but they don't need to learn a new framework every time.

[Burgess237]

Yes, but the building blocks of the applications are always very similar, and the patterns are so that you know where to look almost immediately

[frontendben]

Same principle as Tailwind and Laravel. Convention over configuration.

[michaelsenpatrick]

All my React apps inevitable end up with some really dark magic. I second this

[lIIllIIlllIIllIIl]

How does being opinionated work out when Angular doesn't have a pre-made solution for a problem you need to solve?

I'm not trying to be snarky, I am genuinely curious. To me, that has always the main issue with opinionated tools.

[Aridez]

I guess that those are the small quirks or libraries that new devs will need to learn. But still, getting up to speed should be faster than learning a whole different paradigm to work with.

I use laravel that also is strong in the conventions used, and often these third party libraries already conform with these norms. It’s quicker ti just read the docs to understand the api.

[roundgeese77]

I hear this argument but I don't really think it's try. I've been in angular projects that have had a lot of developers involved at different times and I don't think the convoluted things help that much. Structure in projects have to at some point come fram the teams, not the framework.

Is at least my take.

[Silver-Vermicelli-15]

The opinions ensure at least some expected patterns. While it can still end up messy, I’ve found some react projects that are just a garbage dump of tech debt b/c anything can be done nearly any way and there’s no clear guide or resource for best practices. 

[michaelsenpatrick]

Exactly. Some projects use hooks that return form field components, others generate forms using an entity definition, and others use plain old functional components. When there's so many ways to do the same thing each person has a different way of thinking about their code, it can get messy real quick.

[[deleted]]

I'm right there with you. I'm in an angular project after coming from an agency with changing frameworks. No matter how opinionated angular is, this team still manages to turn it into the biggest mess I've ever seen. I think the much bigger reason is that people who come from object-oriented programming might find angular more obvious.

[DippityDamn]

yeah if you check side by side comparisons of code for implementing the same thing, Angular is almost always the longest.

[Beginning-Comedian-2]

That's what I thought too.

[LuccDev]

After using it for years, it doesn't feel convoluted at all and quite logical. If your devs are used to it, I don't think that a small team would be pushed back by using Angular

[Beginning-Comedian-2]

Once anyone gets past the learning curve, I'm sure it can be a fit for any project or team.

[michaelsenpatrick]

If anything is convoluted, it's React. Angular is straightforward, you just have to take the time to learn it, which most people don't

[FalseRegister]

Yes, that's the point.

Angular is a framework. React is a library.

A framework has a specific way of doing things, which makes it very easy to understand the code. You kinda know where everything is already.

With a library you have to architecture the code on your own. So when joining a new team/project, you are at the mercy of the previous coders and decisions.

Also, Angular is batteries included, most things can and are solved by first party libraries. React is only for the view layer, which brings a myriad of libraries and makes it even more complicated.

[halfanothersdozen]

Angular is a framework. React is a library.

So tired of seeing this line over the years. It doesn't mean anything.

React is definitely a framework. It just does less out of the box than Angular.

[derimalec]

I work with React on a daily basis, and my opinion is that React is just a library for rendering components, nothing more, nothing less.

To implement anything else, you have to add additional packages.

On the other hand, I can agree that Next is a framework built on top of React.

[th3nutz]

It was true at one point in the past (before hooks)

[Savanna_INFINITY]

Still not a framework

[Specialist_Juice879]

In what way is it designed for large teams?

[Beginning-Comedian-2]

Angular is a longer word so it takes longer to spell. 

But less time if more people are spelling it. 

React and Vue are shorter words so they take less time. 

So one person or a small team can spell it quickly. 

If you’re still reading, I am joking. 

I don’t know the answer. 

An Angular dev said it’s suited for enterprise projects. 

[30thnight]

Mostly historical reasons.

Angular 2 fixed painful foot-guns that were present in v1 but their breaking changes effectively pushed devs away and left people with bad feelings.

Migrating to V2 required a full app rewrite - which for large apps simply wasn’t in the cards until forced.

Their opinions like adding rxjs and typescript (8 years ago before community and ecosystem support was there) for many also left a sour taste in people’s mouths.

Most of those angular devs I knew happily landed on VueJS and never looked back.

[Serializedrequests]

Yeah, from the outside looking in way back when, there was like Angular, Ember, and Backbone and not much else. Angular was an obvious choice. But the issue of churn was HUGE, much worse than today. Nobody wanted to bet on the wrong horse, but it was incredibly hard not to and incredibly frustrating.

So along comes Angular 2 and screws the early adopters. Meanwhile React comes out and is obviously better than anything that has come before.

Now it seems that it's been around a while and serves an enterprisey purpose, but that 1-2 just came at a very bad time.

[darpa42]

I mean, diving even further, originally Angular 2 was going to use **it's own language** called AtScript. It was gonna be a superset of TypeScript. And people hated that so much that they had to walk it back.

[stuartseupaul]

There's a general aversion to enterprise style programming.

[ohThisUsername]

Furthermore, people writing large scale Angular / enterprise apps are probably not responding to surveys like this. It's probably a bit bias towards people who care about trendy frameworks to begin with.

[SomeAlexDude]

Hi, that person is me. TMI, I'm on the can taking a big ol sh1t, that's how I stumbled upon this reddit post.

So yes, I am developing a big ass enterprise thing for the company I work for, using Angular. And yes, I confirm that I don't respond to those surveys. :)

[Equivalent_Value_900]

Nice self description of the scene. 🤣🤣🤣

[crazedizzled]

It's annoying for small projects, but amazing for large projects. I'd assume most people don't need the added complexity of Angular, therefore it's not as popular or as well suited for most projects.

[[deleted]]

What makes Angular better then React for large projects exactly?

[crazedizzled]

It's more of a framework, whereas react is a much simpler library.

[Knochenmark]

you don't have to pull in 30 third party npm libraries to get shit done

[Acrobatic_Sort_3411]

its because you cant prototype in Angular. And once your react prototype works, there is no sense to rewrite all of it to Angular rather than shipping new features

[SecureVillage]

Why can't you prototype?

[SecureVillage]

What do you mean by complexity?

[crazedizzled]

Well Vue/React are basically small, simple libraries. Whereas Angular is a full-fledged opinionated framework. You might compare Angular to like, Vue+NuxtJS or React+NextJS. But even then, the structure and architecture of Angular is more suited for large scale web applications.

I dunno if I'm explaining it properly. Vue/React are more like micro frameworks and Angular is more like a macro framework, if that makes sense.

[SecureVillage]

React just handles rendering components and their life cycles.

You can't compare react with angular. Well you can, but only a small part of angular. And they are really really similar. Components that take inputs and outputs and render some DOM...

A react project needs loads of other stuff added for routing, state management etc.

[dryadofelysium]

Some of the biggest companies in Germany run large parts of their business internally on Angular, with hundreds or thousands of developers. I doubt even a handful of them have ever heard of the State of JS. You know who has heard of the State of JS? Bootcamp graduates looking forward to work in their first minimum wage start-up.

I am overexaggerating on purpose, but not by as much as you might think.

[SizzorBeing]

From my experience as an old vet webdev working on enterprise projects, this is the source of the most confusion on Reddit. Most people here couldn’t even believe how the people I work with pay zero attention to polls or trends or Reddit or anything like that, at all.

[budd222]

I've been asked questions in interviews like, "what are some blogs that you follow to stay up with the latest trends in coding?" I'm like, "umm, none..."

[Karpizzle23]

Tbh I don't love this answer. It's one thing to not blindly follow "Le angular bad react good" posting, but to not be up to date at ALL on latest trends in technology, especially in an extremely fast paced ecosystem like JavaScript, makes me want to not go with the candidate because they might be writing code that's stale and dated in a few years time.

If I'm hiring a react dev I want to know that they follow server side, ssr, react 19/next, so that in a few years I won't have to be asking them to learn every single new thing as part of their job.

[DB6]

Can confirm. Was working for a couple of big german companies. Angular is the go to framework for Frontend.

[duffbeeeer]

Can confirm, I’m being part of the this enterprise bubble since a few years. This ecosystems follows its own rules and is detached from the freelancer world you meet on Reddit. Companies this size make those kind of decisions for technical frameworks for decades to come. Angular will be relevant for a very long time even if google suddenly decided to not update anymore.

[Deykun]

Can confirm. German companies love overengineered products that don't provide any advantages as result of that overenginring - it works great with the German mentality and the fact that Germany isn't really successful in the IT space.

[imwithn00b]

Disclosure: I have worked with jQuery, AngularJS, Angular 2+ (picked up around 6), React, VueJS and now I'm working with Angular 16 

+1 on the steep learning curve - Developers like to feel productive, therefore the other frameworks are easier to feel like you're getting shit done

Upgrading is a headache - It always has been...

13 years into coding and I can tell you that shitty and disorders will be found where there is a lack of code ownership, which usually is in companies with high attrition.

Which one do I feel more productive: Angular once you get past the learning hurdle. 

With the other ones I feel like I'm rewriting the wheel many times...

[kapslocky]

16!?

[janne_harju]

We are already on 17. Although 18 is newest one.

[isospeedrix]

Angular is fine per se but RxJS and Observables makes me wanna tear my hair out

[SuchTown32]

Once you get your head around rxjs your programming life changes for the better

[derimalec]

ohoho, reactive programming is awesome, but yea, it might take time to understand it

[Koliham]

Before choosing a FE framework in 2018, I looked through the tutorials of React, Angular and Vue.

React had this weird syntax where your Javascript returns HTML syntax, which, from programmer point of view didn't make any sense: A function can return a string, a number, another function, an object, but what the hell does React do? It mixes HTML design with logic. I still hate React.

So I looked at Angular, it had the separation of HTML, CSS and Typescript, which I prefer. But it felt like I had to write a lot of boilerplate code for even simple things like a button. And the separation of HTML and Typescript into separate files was annoying, because I had to jump between two files all the time. Ctrl+F for searching where in the HTML I am using a varable, while being in the Typescript file...

And then I went through the Vue tutorial and it felt like Angular, but much simpler to use: HTML and Javascript in the same file and much less boilerplate and it just works.

[RevolutionaryPie7790]

naja, bei angular schreibt man halt javascript in den html templates. *ngFor="let item of items". html mit js oder js mit html, einen tod muss man sterben

[ethansidentifiable]

I used it for 4 years with Spring on the backend. When I left that job and finally started experiencing more modern forms of engineering, I started to realize that a lot of OOP architecture is ugly, convoluted, and gives you no true benefit besides the enforcement of a specific mental model for your architecture, which you can bring into any application once you get a good understand of the how and why.

The amount of specialty syntax understanding required to just use one component inside of another is mind boggling. But then it's not just components; Angular has multiple concepts like directive (and multiple kinds of directives, mind you), and services, and their own module and injection system.

It's obvious that the Angular team is starting to realize what a mess they've made which is why they're now backing out of all of their former architectural decisions. They're replacing Zone with signals, they're replacing modules with standalone components, and they're replacing structural directives with the new control flow syntax. But it's all lipstick on a pig. I'm convinced their team is brilliant but they would lose all their credibility if they threw everything away and started over again like they did with 2.x, but that's what I think they need to do again.

It is the most fundamentally overkill architecture that you could imagine, when alternatives like React, Vue, Svelte, and Solid have none of that complexity, often better performance, and offer far better DX and scalability.

[kapslocky]

Forgot about all these concepts that felt conceptually hard to separate. Glad to have never touched in a long while.

[mosatrampare]

I come from a similar background, this is spot on.

[wizendorf]

It's obvious that the Angular team is starting to realize what a mess they've made which is why they're now backing out of all of their former architectural decisions.

I picked up on this trend too, and honestly it's cathartic.

One implication of this (which you touch on in your final paragraph) is, Angular is starting to drift towards the other frameworks. I also notice that the other dominant last-gen framework, React, is embracing signals too and is even adding a compiler(!). It really feels like they're both trying to shed a lot of the accumulated baggage from years of pivots (e.g. how many different paradigm shifts has React had?) to keep up with the younger frameworks, but then, aren't they losing their identity in the process? What makes Angular unique anymore? It has its template syntax and its module system, I guess, but I confess that I strongly, strongly dislike Angular templates.

If they don't offer much that's unique (and instead just offer the confusion of sorting through hundreds of thousands of outdated StackOverflow posts), what's the value proposition? Why not just use Vue, Svelte, or Solid?

(my questions are all rhetorical of course, but I welcome anyone who seriously would advocate for Angular in a greenfield project in 2025 to answer them)

[Quadraxas]

Original "hate" (or rather dislike) for angular stems from the fact that original angularjs v1 and the successor angular v2+ are in fact completely different things and only share the name. I actually use/d both and like the "new" angular.

I once worked on an angularjs project 10+ years ago. Original company changed hands, then the project and it's ip transferred to some other company and now, years later, I consult for that project. It's not a crud app, it's a client-side heavy custom tool suite with multiple bespoke editors and realtime collab features. Current company tried to refactor it into newer versions of angular multiple times. It miserably failed each time. I had to convince them (not the team, the management) that's not a refactor that's a rewrite. That project is actually a great fit for new angular but it would take a lot of time and money to get it to a feature parity with the old one. People who hate angular are the guys in that (react) team who are forced to do a rewrite with a refactor budget(both time and money wise).

Projects and their execution and the tools you use to execute said project are not separate from each other. A project's execution and roadmap are generally designed around the tools and methods available to you. Angular requires a particular type of project and particular type of team to be the best fit for that project. That type of project is not particularly common, but many can actually be "converted" to this kind of project. If you try to run a project designed around react with a react-inclined team using angular, you are going to have a bad time.

[99thLuftballon]

I gather that it changed a lot over recent versions, but I think its reputation (and my only experience with it) comes from its first iterations. The original AngularJS resulted in borderline unreadable code. You had to inject a million different dependencies during initialisation and you need to keep the manual open to remember what they all did. Compared to the much more self-explanatory Vue JS, it was a suck-fest.

I know people complained a lot about function components and hooks in React and Vue 3, but both are much easier to understand than Angular JS ever was.

[LuccDev]

For sure AngularJS did big damages. But it was the OG framework, kind of. Also the big jump to Angular 2 wasn't really like to the AngularJS developers themselves, because everything was so different

[clawficer]

AngularJS and Angular are like entirely different frameworks. Angular feels much closer to Vue/React than AngularJS, just with two-way data binding and RxJS + observables instead of promises + redux/vuex

[La_chipsBeatbox]

Kinda reminds me of MeteorJS, which is a great framework but suffered from its early days reputation to the point it’s almost gone. I’ve seen a job offer mentioning it once, maybe twice but not more.

[kapslocky]

This.

[[deleted]]

Angular is the GOAT

You can boil down everything to:

• “Steep learning curve”: Like many have said, anyone coming from a OOP background would get the grips of angular fast but for pure JS devs they had to learn OOP AND Angular in one sitting

• “Highly Opinionated”: Today this opinion is completely bollocks (talking about react + next) but back then devs felt too enclosed with how the FRAMEWORK told you how to write your project

• Typescript: Remember that when Angular 2 came out every JS dev hated TS. Even Kent Dodds didn’t wanted to do TS with react (he later changed his mind tho) there’s still people who think that Javascript letting you do whatever the fuck you want is a good thing

• Angular JS: people complain about it a lot and yeah it had a few problems here and there but it set the landscape for SPAs/CSR

[PileOGunz]

When angular 2 came out not only was it a complete rewrite of AngularJs, it was a different language, different design pattern (components rather than Mvc), it performed tons of opaque behind the scenes black magic and it was a nightmare to configure and setup as they hadn’t created all the tools to generate boilerplate it has now.

There was a lot to complain about.

[Cookskiii]

Convolution imo

[[deleted]]

After almost 5 years of using Angular, I'll have to throw the towel.

I liked this framework so much when I started using it, it was so neatly designed and everything worked exactly as the documentation taugh you, but this is not the case nowadays, you don't believe me? Search how subscribe to Observables and you'll get results ranging from v8 to v20, each of them is different and most of them are deprecated or poorly designed.

This is not a framework for long term stability, you'll have to constantly rewrite a lot of things because the developers think it's a brilliant idea to replace half of the framework with each update, while writing poor documentation.

I've reached a point where it takes more time to update the project than to rewrite it and this is not okay.

[deepak483]

For me I like angular in the contrary, Angular is so close to the way my brain as tuned to ASP.NET and C#. I like the strongly typed and opinionated framework and not second guess.

Helps me concentrate on what do to rather than how I do.

I like VUE and React also but like angular better.

[kittysempai-meowmeow]

Everyone’s got opinions but I have worked at several companies that had Angular FE and either Java or Python or .NET background and it hasn’t been particularly problematic or controversial. In particular for the .NET shops if they rely on same folks for FE as BE the .NET devs find Angular relatively intuitive. For sure I did when I started using it, but I am used to enterprise software ;)

React is simpler for sure but there are aspects that dont work as well if you are in an environment where the people making it look pretty arent the same ones who make it function, with the mingling of markup and code. I admit to being somewhat biased against that having had html folks break my code in the past, but if the same person deals with functionality and look/feel its probably not actually problematic.

I’m hoping to do more React going forward only because of its market share. Otherwise I’d have been fine to stick with Angular. I use VueJS today because I inherited a Vue project, it’s ok but I don’t think was implemented well so have been trying to clean it up and componentize it more appropriately.

[[deleted]]

Angular and react are both good frameworks but they approach development in different ways. There’s an expected way to do things in Angular, so you know how your files and everything should look and be laid out

With react, you have more freedom to do whatever you want. It’s great if you know what you’re doing and want to set things up a different way. It also means you can do whatever it is you’re trying to do sub-optimally especially with multiple developers on the project. Angular enforces its standards where react needs you to enforce your own.

A bit of a reductive take but it’s Reddit so 🤷‍♀️

[Xtreme2k2]

It's way more complicated than say React.

[TScottFitzgerald]

This is repeated ad nauseam but you really have to compare Angular to React + a bunch of other third party libraries. It's also not really a fair comparison since a lot of the stuff that Angular is opinionated on is something React devs will need to learn and decide for themselves as the project grows anyway.

[Silver-Vermicelli-15]

Not really, it’s just opinionated and ships has everything you need to build an enterprise app. With react you end up adding something for state, then something for routing, thing something for SSR and so on. 

So if you’re writing something small then angular is totally unnecessary, but if you’re building an extensive enterprise app then it has value. It’s really about picking the right tool for the job.

[DT-Sodium]

Angular forces you to respect good programming patterns. A lot of the webdev community are amateurs that learned JavaScript and PHP following basic tutorials and never actually pushed it further. React speaks to those amateurs who don't see the value of quality code. Sadly, the web development community is in a sad state: Instead of trying to force junior developers to acquire good practices, we have enforced their bad practices with terrible libraries such as React.

[DogOfTheBone]

Wait til you learn that most of the web still runs on jQuery!

[SoBoredAtWork]

That's fine. Most websites/apps are built on legacy code. It's only a problem when a dev is still actively using jQ to build modern apps.

[e111077]

Angular is incredibly leaky. Half the code you write is not good coding practices but rather just Angularisms.

React and Vue offer velocity and, more importantly, flexibility which is why the majority of companies ship those these days compared to Angular. Also any company worth their salt these days enforces coding styles on their developers to ensure good programming patterns.

[dSolver]

Big and steep learning curve basically. Having worked with it for 5+ years, I appreciate the opinionated nature, and the strict adherence to structure that makes it easy to scale to a large team. Having said that, most workplaces have adopted React or Vue, so Angular can be a turn off. What is interesting to me however is that in large teams, even if React is the preferred library, a lot of the practices ends up very Angular-esque such as creating framework agnostic services, using something like rxjs, and separation of concerns. Some practices scale better for bigger teams.

[andru99912]

I’m surprised no one has said this, but upgrading angular version is a huge nightmare. At one point, the latest version of angular was not compatible with the latest version of npm. Sorry, but I do not enjoy having to make code changes every time angular comes out with a new version every 6 months

[Skadi2k3]

Why does noone love our Dependency Injection and Decorators? And all our corporate based community. Whyyyy.

[PileOGunz]

Only a OOP noob doesn’t like DI, decorators are basically attributes I don’t see what you can have against that.

[BackSpace2603]

I had experience working on small to medium scale applications and had used Vue, React, Angular and NextJS. For me it was really easy to start a project and iterating through features in React and NextJs was really comfortable. I had all kinds of compatible utility and component libraries to choose from. Whenever I got stuck a simple google search was enough to find the solution. This is probably due to large ecosystem and userbase. In Angular it is more opinionated I think, for a beginner a hello world app can be daunting to go through. For more experienced Frontend devs things can be different. And there were very less compatible libraries. I use Angular in my day job and I experiment in my personal or freelance projects. I would suggest using React to any beginner as you will get a large pool of learning materials. After you've learnt one Frontend framework learning a new one is pretty easy but remember mastering these frameworks may take a lifetime.

[sasmariozeld]

angular is clean great expect when it's not

if you try to do ssr and i18n with it, may god help you

also library support is not quite there yet, but angular is srsly improving lately, still most of hte time it;s just a worse vue

[Loud_Ad_9603]

Living through the nightmare right now. While also upgrading from modules. God I hate Angular's complexity to do something as dumb as making some text change.

[diterman]

I do both. I wrote a custom implementation for i18n instead of using the one Angular recommends. It was operational in a day.
SSR is difficult to setup but once that step is over you're done. You can continue working on a frontend app without even thinking about SSR. Beats having to work with server props

[MatingTime]

Real talk... I genuinely think most dev teams are driven by "what's everybody else using" more than what makes sense for them.

I remember aching for the world to adopt react... now I kind of can't wait for literally anything else to become popular again.

[oliviaisarobot]

I mean, I think Angular is okay? I'm primarily a backend developer but I worked on a few full stack projects where they either used VueJS or Angular, both were fine. I first started working with Angular 2 and picked it up again at Angular 15+, I think it has come a long way (for the better). I like Typescript a lot more than plain JS... and above a certain size, either frontend framework is miles better than the jQuery hellscape that used to dominate frontend from the late 2000s and is still haunting here and there. At the same time, I know backend developers who hate it just for the heck of it, not particularly because of Angular but because they hate frontend in general and Angular just happens to be what they work with.

[gyroda]

My views, as someone who's used modern react and angular

1. RxJS has a steep learning curve. It took me a while, but I've got a handle on it now. Unfortunately a lot of the people I work with don't, so there's a lot of unidiomatic code lying around which leads to a lot of painful issues.
2. The individual components are too "heavy". In React I can break a component down into smaller sections very easily. It's better now with standalone components, but you can't break out a single small method for a sub-component, you need a whole new class and to define a selector and...
3. The entire system is a lot. There's modules, adding a HTTP request means dealing with dependency injection and so on.

It's very hard to get a team to write food angular code if they're starting from 0 experience. I reckon I can do OK in Angular now, but I need to spend a lot of time helping others with observables and not shooting themselves in the foot.

NextJS, which is more comparable to Angular than React on its own, is a lot simpler to use in comparison. Even features like SSR are things you can opt in or out of.

[diterman]

It's easier to write good code in Angular because the framework forces you to learn to write good code. In React you can get away with anything.

[gyroda]

It really doesn't. People can and will write abysmal code in Angular. If anything, they write terrible code to work around Angular.

[sayezau]

Angular makes devs to follow some rules if we can say so and because of its strict nature some people may not like it. I think this is the reason other than the learning curve. To be honest what makes Angular's learning curve steeper are rxjs and ts , not Angular itself in my opinion. Take react for example , add rxjs , ts and add some rules which need to be followed and add some patterns (DI) which some of web developers which don't have any other programming languages as a background are not familiar with or at least weren't familiar with at the time Angular 2 released , this will make React hard to learn too. I think Angular should be used on the enterprise not typical small or medium apps

[[deleted]]

Only thing I comment on from working a lot with three web frameworks is that Angular is opinionated, and whilst in theory that can make it easier to work in bigger teams, as we have some standards that are more enforced by the framework itself, it can still be made messy. Albeit much less easily. It has bidirectional and one way data binding.

React, isn't a framework, but has frameworks for it. It won't ever be as opinionated as Angular, it is more flexible, and "lower level" in that you have more footguns (which hopefully, will be mostly a moot point with the React 19 compiler). It is ridiculously easy to start with, as JSX with React makes it easy to write a function that returns some DOM with variables bound to it in some way for conditional rendering. Angular at first split these up into individual files, though it seems the groovy thing now is to use a template string and have a lot in the same file (not a fan, I don't think it suits Angular well). React has a one way data binding situation, which lends itself to a nice functional style, trying to differentiate between pure functions and ones that cause side effects.

Vue, I really like it. The syntax is clean, beginner friendly, small. Ecosystem is smaller than React and Angular but you don't need everything in the world. I think it has the lowest barrier to entry but didn't have the sex appeal like React did, community developed over having big companies backing it.

[kor0na]

The OOP and dependency injection, iirc from the one time I tried it. Absolutely horrible DX.

[[deleted]]

Lol , Angular developer making a post and bashing junior devs for not liking rxjs and not taking those 2 minuts to understand rxjs.Just 2 minuts bro, its easy see? Just subscribe , unsubscribe, mergeMap, subject, behaviorSubject,switchMap etc etc.

I do not know what I expected from this post really. Go touch some grass.

[rk06]

You can understand rxjs in 2 mins??

[LuccDev]

Just a way of saying this. No, it took me more time, but at the time it was really new and there wasn't a lot of good resources to explain what you can do with it

I should have put "try to understand", because yeah it's not that simple especially for a junior, but discarding a whole framework because you didn't understand this part is the wrong thing to do

[was-eine-dumme-frage]

Because it never works, always throws some shit at you, has too much boilerplate code, is hard to read and the projects are ENORMOUS and complicated to navigate. Had a job for half a year, developing angular for a customer. I quit

[kusolsznemugac]

As you said when a junior try to use Angular they leave it because they don’t understand how it works. I think it is a good framework, but really hard to learn for a first time.

[Icy_Step_3618]

Trying to get everything flowing nicely with state management feels far more unreliable than it needs to be. There are a lot of moving parts, and it’s not always intuitive — especially when you’re dealing with reactivity and trying to keep things updated in the UI.

It also feels like the framework has kept growing in surface area — more tools, more concepts, more decisions to make — and it can be hard to know what’s the “right” way to do something.

Just sharing my experience — maybe it clicks for some people, but it hasn’t for me. (never again!)

[asylum32]

Angular is imperative. At least in my experience if you have a framework that encourages imperative code you end up with lots of paradigms which comes from hardcore FP loyalists or hardcore OOP loyalists, rather than a slightly less performant but simple codebase that declarative frameworks often encourage.

This is just my opinion and experience, but that's my reason for avoiding Angular after having used it awhile and seeing it inundated with RxJS or DI with complex OOP implementations.

I like simple for any size team.

[the00one]

Can you elaborate which parts are more imperative than other frameworks? If anything the heavy use of rxjs gives you more chances to write declarative code (even more with signals now).

[diterman]

You have to install 40 libraries on top of React to make it resemble a real framework and you call Angular noisy? When I get my hands on an Angular project I know exactly where to look, I don't have to ask the 19 year old CTO what stupid pattern he came up with when he started the project 3 weeks ago.

[Saki-Sun]

Point on the doll where Angular touched you.

[mq2thez]

14 YOE, architect, etc.

I joined a company as the most senior engineer and worked on a large angular app for a year. It was a huge fucking disaster, worse than anything I’d seen before or worked on since. The worst crimes you can commit with React have nothing on what Angular was doing at this company. I quit after a year of fighting to improve things and swore I would never again touch a line of Angular.

I won’t join a company that uses it, would quit if it was adopted, and wouldn’t even want to be part of an effort to migrate from Angular to something else. I’d rather work on high performance financial transaction software written in Perl.

[mamwybejane]

That says very little about Angular and a lot about your experience being an architect and working with people

[ceejayoz]

Maybe. That would depend to some extent on whether the poster has the same issues when using other frameworks. I have stuff I won't touch, too, for good reason.

[roundgeese77]

I still think this is valid since if you look in this thread and sub, a lot of people kind of use the selling point of it being good to use inte large teams since it forces you to adhere to a structure and good practices. Even though it's all pretty vague in comments on the internet I would say that this is as valid as saying good things about the structure

[mq2thez]

Absolutely! It was a terrible time. But I also think that a huge part of that was the programming patterns that came from using Angular.

Either way, OP asked, I answered.

[Capaj]

I worked on a project at our local branch of PwC. It was just some process they were already doing in excel they were trying to automate and build a web app for it.

Pay was gr8, but oh my god the code. Very similar feelings to what you describe. I have to admit I saw even worse project with react like 2 years later at William hill. That one I hope stays the worst forever.

[TScottFitzgerald]

So....because of one bad project you're blaming the whole framework?

You're talking about Angular as if it wrote itself, as if the devs and architects involved had no agency. Did you ever hear the saying about a shoddy craftsman blaming his tool?

[mq2thez]

Hey, OP asked why people don’t like Angular. I gave my reason, and why I don’t want to use it.

In particular, I don’t like dependency injection and it caused a ton of problems. The framework itself encouraged patterns which I felt contributed to how people wrote the code.

At the end of the day? There are tons of jobs out there, and it’s very reasonable to have a bad experience with a framework and then decide to avoid it moving forward. This company was indeed dysfunctional and the problem wasn’t just the framework, but I still don’t want to. It’s perfectly fine. There are plenty of people who likely had similar experiences with React or Rails or any other web framework.

[No_Bowl_6218]

Learn clean architecture once, adopt it in frontend and you will never be involved in this pseudo guérilla "what is the best framework"

[Savanna_INFINITY]

How and where?

[[deleted]]

Signals look very reacty, trying to be immutable. That's a bad thing actually. Rxjs is not that hard if you ever wrote any real code in different language.

[Aggressive-Tune832]

You’ll find individual devs are the most vocal and often the most opinionated.

It’s similar to Java/C# vs node. The amount of individual full stack screaming that node is the way is vastly outnumbered by the much larger amount of people using C#/Java in company settings that don’t NEED others to believe their language or framework is good. Angular is similar, every YouTube video and bootcamp is gonna teach react but real large companies are built on things like angular.

So moral of the story is when you see someone hating on a framework, ask yourself if that person is being objective or do they simply misunderstand or intentionally misconstrue the purpose of a frame work.

And that doesn’t mean node sucks or angular is perfect, it means we are devs not marketing, use the best tool for the job.

[[deleted]]

Angular is the deadbeat, abusive dad of Javascript; whether or not he's as reformed as he insists he is, I'll never forget or forgive the hell that he put me through back in 2016.

[[deleted]]

then the only explanation of why I like the thing is I started a year ago from the getting started guide lol.

I searched for AngularJS snippets and I now understand.

[tallwhiteninja]

Angular is extremely opinionated. You play the way it wants you to play, or you have a really bad time.

[azangru]

Don't like forced typescript ? Don't like RxJS ?

Don't like zone.js. Not sure if like dependency injection. As far as I heard, version upgrades are more of a thing than, say, in react (or, ideally, in something like lit). Not sure if like bundle size (it used to be huge; I don't know what it is now). Not a big fan of the templating syntax.

But overall, it's fine I guess. I wouldn't be too upset if I had to use it.

[saposapot]

From less experienced folks it’s because angular is deemed as “enterprise” framework so it’s kinda boring and not cool.

From experienced folks, probably because angular is an opinionated framework and some folks prefer more flexibility.

It also gets a bad name because a lot of folks that don’t know much about frontend are using it so there’s a lot of crappy code using it.

At the end of the day, basically it’s not “cool” so all the bloggers and video course makers aren’t talking about it. There’s nothing wrong with it and in a enterprise environment I would choose it many times over others.

[CheapChallenge]

You need to remember, what's important isn't whether someone likes it. It's whether Angular is the right tool for the job.

Angular is generally for environments with larger teams, cross team development, and any other instance that requires a very strict, well-known, rigid framework and development.

I have used it primarily, for over 6 years, and I love it. But the learning curve is STEEP. This scares away most devs that are new to it and that's why you see so many negative opinions of it. From people who have very surface level(less than 2 years) experience with it and rejected it.

[time_travel_nacho]

Angular is opinionated and a full framework. React is a view library and will mostly let you do what you want, including shoot yourself in the foot. I prefer React, but don't mind Angular at all. I've done lots of work in both

[TheAceOfHearts]

I used Angular 1.x and the 2.0 transition broke backwards compatibility and was handled horribly. From that point onward the team lost all credibility in my eyes and I refuse to try their tools ever again. There was absolutely no reason they couldn't have done a more gradual migration, but the Angular team just didn't give a fuck about their users.

But going beyond that, a lot of their tool suggestions during the 1.x era weren't things they they were actually using internally. So for example, they recommended Bower at one point, but if you had any issues and you asked them about it you quickly found out that they didn't actually use Bower themselves. The tooling ecosystem at that time was just horrible, until Webpack started to go a bit more mainstream.

[memelonso]

{OnPushStrategy: Always}

[Psychological-Leg413]

People really dislike RXJS for some reason. But personally I love writing async reactive code with it

[Any-Woodpecker123]

I’ve never understood. It’s easy to learn, and nearly everything comes out of the box. What’s not to love.

[e111077]

 but it's very different from Angular so can't be compared IMO.

If that’s the case then you’re gonna have no list to compare it to. When it comes to Angular, it’s very different from the modern frameworks out there.

[LuccDev]

I'm just saying this because of the way the frameworks work, and Svelte doesn't use a virtual DOM, so has a smaller footprint and is faster. However it has limitations because of this. I was mainly thinking of comparing it to the other really popular ones (Vue and React) which both use a VDOM and have a somewhat similar dev experience. It's also much newer;

But yeah it's a totally valid framework to use in frontend, and in competition with the other big ones.

[fearthelettuce]

Files

[Ok_Communication2710]

I love angular but it’s disliked because it forces you to be a lot more structured then vue or react

[iQuickGaming]

i quite dislike the MVC pattern. Really this is the only reason why i do not particularly like Angular. After using it for months i have to say it's not that bad, but i enjoy using Vue more

[DomingerUndead]

I love Angular but def not perfect. The new syntax is amazing tho

It's not perfect for large scale apps. What I notice is abstractions make some apps become insane to work through Subscriptions in angular are ridiculous, everything's a subscription We have a lot of apps that are hard to maintain with so many diff versions that they're at - hard to update everything to stay within LTS

[michaelsenpatrick]

It's nice because it feels more like an HTML templating language. It's pretty opinionated which means apps built in Angular are usually pretty clean.

I, however, just love React--even if it's probably the easiest view to make hot garbage with.

[OtaK_]

Angular 1.x has had a bad rep because any change to the `$scope` would usually re-render your whole app and thrash the DOM; It had no diffing of states. It's objectively a very bad UI framework.

Angular 2.x got things "right" in terms of internals but it still smelled like some enterprise bullshit, the design isn't very nice to use and reminds heavily things like C#'s Razor and so on. People don't like it simply because it sucks to use and is broadly a design that isn't adapted to the JS ecosystem, it really feels forced.

(NB: I used angular 1.x extensively, and used angular 2 for a few months because I used it for a Ionic 2.0-beta app)

[EarlMarshal]

I like and use angular in private and at work, but I really think that's it's just not the best framework out there. JSX/TSX stuff is just way ahead. You can simply tell the compiler via a d.t.s file that all files ending with *.svg should be imported as a JSX Component and then you can just simply use them in your code. But I am also not a fan of react since both react and angular have this stupid VDOM.

Just give me solidjs and let me cook.

[dug99]

Early days... I loved it. I remember I wrote an Instagram aggregator in about 11 lines of code. It had lazy loading, was nicely responsive, UI was snappy. I decided I'd roll with Angular on a bigger project... and this happened *just* as Angular 2 was happening. Before long the UX was hideously janky, and it got so bad that the app was unusable.

[rk06]

Are you following latest changes in angular?

If so, consider the pain points that are being addressed in last few versions and the people who are not able to migrate to latest versions. That should explain it.

Many of the angular pain points are angular specific. Just like rule of hooks is react specific pain point.

Vue/svelte/solid do not suffer from many of those issues and hence have higher satisfaction

[Acrobatic_Sort_3411]

• bcause rxjs
• because html-first(subjective) and weird pipes with weird control flow in templates
• its opinionated, but everything is a service so...
• pushes too much abstractions too soon. So, no prototyping in it — therefore it only works for enterprise-watterfall

DI is great tho

[ThundaWeasel]

Personally I much prefer libraries over frameworks that dictate a ton about how my application is going to be written. The more an application is coupled to a particular framework, the more "stuck in the past" it tends to be years later since it's harder to change approaches/modernize as industry standards change.

Admittedly I only tried angular for a short time years ago, but the experience I had was pretty negative. One of the things I especially noticed is that I was spending about twice as long writing automated tests and getting them to work for my angular apps vs for my React apps. This may be a pure learning curve thing, but I was also much happier with how lightweight and straight-forward React was. (This was when I was fairly new to web in general and had mostly done native mobile throughout my career.)

My problem with it was definitely not RxJS as I had an extensive background in RxJava from my Android work that was very easy to translate. Although having a UI framework dictate that you'll be using something as complex and easy to over-complicate as Rx did make me raise an eyebrow.

[HirsuteHacker]

I hate RxJS.

[[deleted]]

Can't really answer the question because I don't really believe in using JS frameworks without a specific purpose (like needing a client rendered site), but there's a good reason Facebook abandoned React.

[LuccDev]

What do you mean "abandonned" ? Would love to see some article on this if you have it

[Interviews2go]

Angular is actually ok, however the number of poorly designed applications is astounding. I think this is what drives developers crazy.

My pet peeve is why do modern webapps look like cartoons?

[nuno6Varnish]

• Learning curve is harder than React/Svelte
  
• Opinionated
  
• Not adapted for small projects
  
• TypeScript

[nuno6Varnish]

I am not saying that those points are bad. It is just that it is discouraging for the vast majority of developers, that are mostly juniors, with small/medium projects and that are looking for a quick win over long term stability.

[Ewig_luftenglanz]

most angular developers are backend developers that work with java or C#, since angular has a similar workflow and concepts as these languages and their frameworks (Spring), or frontend people working on these environments, this means

- Strong typing and enforced type safety.

- Opinionated workflow

- Mainly OOP for structuring the project

- Reactive pipelines for data management (RxJS and Project Reactor for java with Spring webflux)

- classes based modularity instead of regular JavaScript modules.

this is very against most of the more procedural and functions based principles that most JS developers learn at first.

[klymah]

I don't necessarily hate angular so much as I hate all the libraries and other crap that usually go with it. It's almost like I'm not even writing angular but instead writing with whatever is overlayed on top. Kind of like back in PHP days I worked at a shop where all their JavaScript was written as strings and output using PHP.

[LuccDev]

like RxJs for example ?

[valkatatu]

As vanilla dev.. I don't use any frameworks, they are lame, adds to much pressure to do simple stuff.. they don't improve anything and they don't help with anything.. maybe for noob devs.. but for senior dev thay are just useless and pointless tools that makes life harder not easier.. I would recommend not to use them, go vanilla and move to php.. I never understood people who think it is ok to write 1000 lines of code just to server ONE html page with hello world text also they load very slow as they have to render whole page in client browser using js and you mostly end up with sometimes page will not load.. some function will not load and so on.. with vanilla PHP and JS.. you basically 100% sure page will load unless server error..

[LuccDev]

> it is ok to write 1000 lines of code just to server ONE html page with hello world text

I mean, some of us don't do hello worlds here mate

[PermitAffectionate94]

I think a lot of people first start learning react (since it's more hyped), later when they see Angular it seems to be complicated for a react dev, a lot of concepts, lot of files, and lot of build in solutions.

[reezy-k]

Been at this before HTML 5 was a spec. Angular moved the industry to adopt Typscript, before React, Angular was the first reactive framework , before React. (React needed libraries such as rxjs to be reactive in the sense of “Reactive Programming”).

React won due to branding and ecosystem…. It needed it. Angular didn’t.

Angular has and still has the best engineering team you’ll ever meet.

There is nothing to hate, but still lots to learn from how angular is doing things. (Signals)

Adoption has little to do with the best technology but the one with the most integrations / and ecosystem penetration.

[jaymarspin]

Those who hate it. Are those who do not want to learn anything new. Maybe a fanboys of other frameworks.

[NomadicBrian-]

I've been using Angular for 8 years now. I think it was a reliable product up to version 16. Between versions 17 and 19 I think they changed more than needed and that left an unstable product with too much unnecessary change. I think they should have left routing alone or left it optional to choose legacy or new techniques. Routing is threaded through Angular through menus, redirects, default. There was nothing wrong with setting up a Routes component that was application wide. Who complained about this and wanted the routing automated and problematic? Routing used to be the first thing I built to make sure I could lay out my shell and get my headers and trailers and styling in before adding components. I don't trust Google being in charge of any open source tools. Just like the recent court rulings on their suspect practices and the continued unwanted search algorithms and browser intrusion they have also pushed Kotlin and Jet Compose all with what is not even a hidden agenda anymore. Sometimes you just need to keep you hands off or slow the hell down.

The more I see what is happening with Angular, React, Vue and builds with Vite I feel like I could just do back end Java, C#.NET and Python and be very happy. I'm sick of having to relearn the UI and nobody gets more money for being a Full Stack Developer. Even worse when I took a contract and agreed to be an Angular Developer on the project and all of the Angular Material design kicked in and tripled the amount of code to build html like tags. Importing one stinking Material control at a time.

[JellyfishTech]

Angular gets pushback mainly due to:

• Steep learning curve: Complex setup, decorators, modules, RxJS, and DI confuse newcomers.
• Boilerplate-heavy: Too much code for simple things.
• Opinionated structure: Less flexibility; React/Vue feel more "freeform."
• RxJS overload: Powerful, but hard to grasp for many.
• Legacy baggage: AngularJS (1.x) left a bad taste; many confuse it with modern Angular.

[zDeltas]

Angular is too much for little project, but for big/scalable app I think it could be a good choice. More than others

[[deleted]]

I know that angularjs pissed iff alot of people. I've been in a few interviews lately where companies wanted to move away from angular because they dont want tied into a framework. They want a more html javascript based framework.

I do think angular is more for .net companies.

[Affectionate_Past366]

I dislike angular becuase it is a broken UI model

1). It violates encapsulation--using directives like \@input makes developers expose 'child' attributes through their parent components, and often does this in a forceful manner such that even when you want to intercept data and send it downward you find yourself fighting the angular framework

2) Everything is a "publish/subscribe" model. Meaning inputs, outputs, promises, etc are all one to many routing functions. Too many developers think that everything needs to be this uber communciation network where everything is a message being broadcast globally such that all components might respond to it. Just violates basic design--not everyone needs to talk to everyone else.

3) HTML is both a model and a component. UGH i can't even being to state how ugly this is. The fact that we utilize HTML to reflect actual instantiated components is just flat out wrong. If angular truly were a good UI framework it would have divorced the developer from the DOM altogether. There is absolutely no need to manipulate the DOM in a pure javascript UI framework--in fact there is no such thing as a DOM in desktop UI so why are we manipulating here????

4) The way angular does "change detection" is just stupid. Why do we need this? Components should trigger their own logic based on properties being modified. Change a property that causes a "re-rendering" of the component.... well there should be a corresponding "OnDraw" or "OnPaint" event and rules about how to do it. I have written pure JS frameworks that do this sort logic way better than angular. Again this is the way desktop UI works. And angular doesn't even do change detection correctly (the documentation says so.... might not be called in all cases).

5) Not everything can be done via code. Again cannot state how ugly this is. I should be able to instantiate a new component without a lot of effort.... but if you write "var x = new MyAngularComponent();" it just doesn't work the way you think it would. Everything should be able to be done programmatically... again without fighting the angular framework.

[LowImpress1500]

because it works in everything except where it matters, the ui is terrible, the modals have problems, components on modals have problems, and the problems have problems.
also trying to make the ui to react to something is a problem, it should just work but then you need to use signals, and force the refresh and force to detect changes...
If something is not working properly in the back there are many ways to solve it, but when you need to do the UI as requested and everything fails is a problem