4 ms·

I worked with React almost exclusively for ~5 years. I got so fed up with everyone reinventing the wheel on every project, coming to Angular (late) was a massiv

by trhoad 4y ago

I worked with React almost exclusively for ~5 years. I got so fed up with everyone reinventing the wheel on every project, coming to Angular (late) was a massive breath of fresh air. I now spend more time building valuable features rather than discussing changing state management libraries and people banging on about hooks all day long. YMMV, and I'm certainly in the minority, but I'd probably choose Angular over React for any new projects now, personal or professional. The only thing I really miss is that JSX is much more ergonomic and the devtools for React are a bit better.

coding123 4y ago
I would have to agree with this sentiment. I think one of the best things about hooks in general is that it put to rest all the third party state management libraries. At least now you can just agree with most people and move forward with hook state. That being said, I think the ergonomics in React development (JSX) are SOO much better than Angular that I still prefer it.
- trhoad 4y ago
  JSX is the best thing about React, and the Angular templating is worst thing about Angular, so I can certainly empathise with that being the tipping point.
moystard 4y ago
My experience is very similar to yours, and I concur with your conclusion. After 5 years of React, I joined a new organisation as engineering lead, and the team had embraced Angular before I joined. Coming from the React/Next.js world, I was really puzzled with that decision as I still had in mind the trauma of the Angular.js -> Angular migration and the breath of fresh air that React had represented at the time. As most engineers out there, I had an urge to stick to what I knew would work, but I resisted that urge and gave Angular a chance. I do not regret it; Angular and the structure the framework provides is a game changer for a large project; the conventions make the code and the architecture predictable/testable/scalable. Our time is spent on delivering value for our users. This is, in my opinion, the best quality a technology can have when working on a fairly large project.
jeremycarter 4y ago
This is my sentiment as well. Although trying convincing people to give it a genuine try is difficult.

by trhoad 4y ago

coding123 4y ago

I would have to agree with this sentiment. I think one of the best things about hooks in general is that it put to rest all the third party state management libraries. At least now you can just agree with most people and move forward with hook state. That being said, I think the ergonomics in React development (JSX) are SOO much better than Angular that I still prefer it.

trhoad 4y ago
JSX is the best thing about React, and the Angular templating is worst thing about Angular, so I can certainly empathise with that being the tipping point.

moystard 4y ago

My experience is very similar to yours, and I concur with your conclusion. After 5 years of React, I joined a new organisation as engineering lead, and the team had embraced Angular before I joined. Coming from the React/Next.js world, I was really puzzled with that decision as I still had in mind the trauma of the Angular.js -> Angular migration and the breath of fresh air that React had represented at the time. As most engineers out there, I had an urge to stick to what I knew would work, but I resisted that urge and gave Angular a chance. I do not regret it; Angular and the structure the framework provides is a game changer for a large project; the conventions make the code and the architecture predictable/testable/scalable. Our time is spent on delivering value for our users. This is, in my opinion, the best quality a technology can have when working on a fairly large project.

jeremycarter 4y ago

This is my sentiment as well. Although trying convincing people to give it a genuine try is difficult.