This summed my experience with it as well. Coming from Angular and moving to React, you can appreciate the training wheels you get with Angular while bringing what you've learned to React. What causes me to stick with React is perhaps the level of flexibility and state-awareness. Angular requires you to pipe async traffic through god-knows how many observables and chains, while in React, all components receive the state snapshots. If you hide rxjs behind a layer of abstraction, I'm sure you can eventually achieve a similar experience with Angular, but the default change detection will probably destroy your app in the meantime.
The issue with Angular vs React is that it's not a "this one is better for x size app" problem, it's a "React is a toolbelt and Angular is a prebuilt template with strict rules" problem. You can use React the same way you do Angular, or you can use React for different things. A software engineer should be aware of the differences and should not expect the same things from each technology.
I am a Full stack .NET Developer, I like to work with C#, Asp.Net Core, SQL, Mongo DB, Azure, JavaScript...
Always eager to learn new technologies. I am here to share, ask & eventually learn.
I completely agree with that. In my conclusion, in fact, I say exactly that. Having both in my tool belt allows me to essentially get the best of both words.
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.
This summed my experience with it as well. Coming from Angular and moving to React, you can appreciate the training wheels you get with Angular while bringing what you've learned to React. What causes me to stick with React is perhaps the level of flexibility and state-awareness. Angular requires you to pipe async traffic through god-knows how many observables and chains, while in React, all components receive the state snapshots. If you hide rxjs behind a layer of abstraction, I'm sure you can eventually achieve a similar experience with Angular, but the default change detection will probably destroy your app in the meantime.
The issue with Angular vs React is that it's not a "this one is better for x size app" problem, it's a "React is a toolbelt and Angular is a prebuilt template with strict rules" problem. You can use React the same way you do Angular, or you can use React for different things. A software engineer should be aware of the differences and should not expect the same things from each technology.
Yes agree. Thanks. :)
I completely agree with that. In my conclusion, in fact, I say exactly that. Having both in my tool belt allows me to essentially get the best of both words.