3 ms·
I used Angular at my last company. After having used react for many years and then experimenting with svelte, Angular (even the most modern versions) felt like
by cjhowarddev 4y ago
I used Angular at my last company. After having used react for many years and then experimenting with svelte, Angular (even the most modern versions) felt like it was always in my way.
Bi-directional data binding and the isolation between style, structure, and logic felt was less productive. Angular has some nice properties, like dependency injection built in, but you can circumvent many of those needs with a functional component tree in react (or limit the surface area across components). The simple fact that you need @Output event emitters to handle callbacks is a good example of how bloated it feels.
It may be that I don't know nearly enough about Angular but even after a year of doing my best to learn the idiomatic Angular ways I wasn't impressed.
- Zetaphor 4y agoAs someone who is now a couple years into using Angular after a number of years working with Vue (since 1.0) your observations are accurate. It doesn't really get any better as you become more familiar with the framework.
- deleted 4y ago[deleted]
- bergenty 4y ago
- shadowwillow 4y agoI have found it better practice to generally emit via a service BehaviorSubject that other components subscribe to rather than passing thru outputs and inputs generally speaking.