3 ms·
I've got experience with Angular 1, 2, React+Redux, with teams of 5+ For me, the real problems in web app development are 1. State management 2. Side effects
by tomelders 10y ago
I've got experience with Angular 1, 2, React+Redux, with teams of 5+
For me, the real problems in web app development are
1. State management
2. Side effects
3. View layer performance
Angular pales by comparison to things like React+Redux which were born out of necessity, and as such, tackle those issues with laser like focus.
Angular doesn't feel like it was born out of necessity, but out of some desire to just build a framework. As such, it's complicated and magical feels clumsy by comparison.
When combined with things like Immutable, Sagas, and ReSelect, the Redux/React style of architecture (feel free to swap out Redux or React for whatever you prefer) is so much more practical and useful compared to Angular.
I don't know what it is that makes Angular popular with back end developers, but they seem to be Angular's biggest supporters. I consider my self full stack, but front end first, and I've noticed that people like me tend to favour libraries over frameworks. There's obviously something that is informing each groups opinions on this matter, but I don't know what it is.
- kevindqc 10y ago>When combined with things like Immutable, Sagas, and ReSelect, the Redux/React style of architecture (feel free to swap out Redux or React for whatever you prefer) is so much more practical and useful compared to Angular. You can use all that with angular 2. I am. Redux -> @ngrx/store Immutable -> same Sagas -> @ngrx/effects ReSelect -> same Example here: https://github.com/ngrx/example-app https://github.com/ngrx/example-app
- tomelders 10y agoBut why? If you're adding all of that to make Angular work the way you want it, what benefits are you actually getting from Angular?