Interesting to read this perspective given that I've just gone through a similar experience: I worked with AngularJS a few years back; then worked with React (+ TypeScript) and just completed an Angular project. I do totally agree with your closing thoughts: ultimately these libraries/frameworks are all just tools and every tool has its pros and cons; but I would never use Angular for a personal project and would only recommend it if the perceived benefits are absolutely essential.
The main argument I'd make against Angular is that it is comparatively complex: there is a lot of boilerplate to learn and you land up generating a lot of project code that at some point you will have to come back to and work with. The CLI does help generate the boilerplate; but you'll still need familiarity in order to work with that code.
You can argue that the complexity is justified because it provides robustness and scalability; but that's also what makes Angular an expensive choice. Onboarding of new devs will take longer (I found the documentation really hard to work with: far too wordy) and working with code just takes longer. Over time that all adds up and you will have to pass on that cost to your clients...
TBH I think Angular's reputation is justified; but that doesn't mean it doesn't have its place :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Interesting to read this perspective given that I've just gone through a similar experience: I worked with AngularJS a few years back; then worked with React (+ TypeScript) and just completed an Angular project. I do totally agree with your closing thoughts: ultimately these libraries/frameworks are all just tools and every tool has its pros and cons; but I would never use Angular for a personal project and would only recommend it if the perceived benefits are absolutely essential.
The main argument I'd make against Angular is that it is comparatively complex: there is a lot of boilerplate to learn and you land up generating a lot of project code that at some point you will have to come back to and work with. The CLI does help generate the boilerplate; but you'll still need familiarity in order to work with that code.
You can argue that the complexity is justified because it provides robustness and scalability; but that's also what makes Angular an expensive choice. Onboarding of new devs will take longer (I found the documentation really hard to work with: far too wordy) and working with code just takes longer. Over time that all adds up and you will have to pass on that cost to your clients...
TBH I think Angular's reputation is justified; but that doesn't mean it doesn't have its place :)