Hey Anthony, nice to meet you! I'm kind of the opposite, coming from Angular and end up working in React :p Love your enthusiasm in making various side projects!
Personally, React was my first front-end library. I then changed jobs and ended up working on an AngularJS codebase. Eventually, I was in a position where my company was choosing between React and Angular because AngularJS was being discontinued. They chose Angular. It's nice because it gave me more experience of different front end technologies. I like it too, though I sometimes wonder if some things would have been easier in React - I guess they say the grass is always greener on the other side :)
I felt the same for the saying "the grass is always greener on the other side"! When I look back to Angular and the problem my previous job, I felt I can do better now haha. Maybe because I'm more used to React, I still prefer React. Some upsides are that, there are way more resources and open source packages and community around React. And it feels more JS/TS (while Angular feels more C# personally), flexible and less opinionated to me.
However, greater flexibility comes as a cost that it might be easier to write low quality code. Also, when talking about React as a library VS Angular as a framework, React dev might need some more libraries to make it complete, while Angular is more "batteries included" with routing and other utils. My last word - it might be a question of preference :p not something that has an absolute answer.
Completely agree. Angular feels more opinionated, and 'complete' as a framework. But that also means projects can need a bit more setup.
I think it ultimately depends on the type of project. Smaller projects might benefit from using React while larger and more structured projects might be better with Angular. That's no criticism of either and certainly not a rule either - just the impression I got so far from using both.
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.
Hey Anthony, nice to meet you! I'm kind of the opposite, coming from Angular and end up working in React :p Love your enthusiasm in making various side projects!
Hi Patrick
Was React something that you chose to do?
Personally, React was my first front-end library. I then changed jobs and ended up working on an AngularJS codebase. Eventually, I was in a position where my company was choosing between React and Angular because AngularJS was being discontinued. They chose Angular. It's nice because it gave me more experience of different front end technologies. I like it too, though I sometimes wonder if some things would have been easier in React - I guess they say the grass is always greener on the other side :)
I felt the same for the saying "the grass is always greener on the other side"! When I look back to Angular and the problem my previous job, I felt I can do better now haha. Maybe because I'm more used to React, I still prefer React. Some upsides are that, there are way more resources and open source packages and community around React. And it feels more JS/TS (while Angular feels more C# personally), flexible and less opinionated to me.
However, greater flexibility comes as a cost that it might be easier to write low quality code. Also, when talking about React as a library VS Angular as a framework, React dev might need some more libraries to make it complete, while Angular is more "batteries included" with routing and other utils. My last word - it might be a question of preference :p not something that has an absolute answer.
Completely agree. Angular feels more opinionated, and 'complete' as a framework. But that also means projects can need a bit more setup.
I think it ultimately depends on the type of project. Smaller projects might benefit from using React while larger and more structured projects might be better with Angular. That's no criticism of either and certainly not a rule either - just the impression I got so far from using both.