3 ms·
Yeah, this description doesn't sit with me very well, either. I fully support the argument that Angular is not a good choice because React is more popular and h
by snapdaddy 4y ago
Yeah, this description doesn't sit with me very well, either. I fully support the argument that Angular is not a good choice because React is more popular and has a larger pool of developers, but not that it is more complex.
I too would like to hear about what complexities you are encountering and if they are incidental or necessary complexities.
- wokwokwok 4y ago? This reads like too much cool aid. Angular is an entirely application stack, “choices made for you”. uses dependency injection out of the box, has a complex module system (eg. How you used to have import Material components one by one). It’s observables all the way down. How can you argue that’s not complex? It’s super complex. I mean, let’s just take an example, say, making a library… https://angular.io/guide/creating-libraries https://angular.io/guide/creating-libraries Now let’s look at https://kit.svelte.dev/docs/packaging https://kit.svelte.dev/docs/packaging Quite the difference. I’m a modest fan of angular because it produces good stuff… but not because it’s simple or easy to learn. You get good solid engineering outcomes with it.