For me, as primarily a backend dev, the argument was that it's a framework, unlike React, so you get an everything-in-one solution which is quite easy to setup and use.

Given that Google still hasn't killed this one yet, it's also a mature platform with plenty of articles online on how to use it.

IIRC the license was also better than React's, at least last time I checked.

Not sure on what the landscape looks like today, but when I was making the choice, the internet didn't seem to consider other solutions to be competitive with either React or Angular.

[–] lesnout27@feddit.org 1 points 1 month ago (1 children)

What would be good other solutions?

[–] Eiri@lemmy.ca 3 points 1 month ago

Vue and React are popular alternatives.

Lit is a less popular alternative that's 100% compatible with native WebComponents, and I've been interested in it ever since I first heard of it.

[–] Zangoose@lemmy.world 1 points 1 month ago

To me at least angular makes a bit more sense than React's way of doing things does. React tries to be functional with its components and yet it seems like they end up basically trying to mimic classes with useState and useEffect. To me Angular's class-based approach makes a bit more sense (though I am primarily interested in backend development more than frontend so that could be why)

It does kind of fall into a lot of the traps of Object-Oriented programming though so I can see why a lot of people don't like it