I've worked on Angular stuff for years because my employer won't let us switch. Angular uses too much abstraction.
Angular does crazy things to the templates, to the point that trying to build your own UI widgets is a recipe for pain.
Template meta-language is stupid. It's just similar enough to JS that you mess up the syntax all the time and never really stop. Since it's not just JS like JSX there's not good linting support either.
Related, stupid "pet features" and hydra syndrome. Like Pipes. Why does Angular use these weird pointless things when you can do the same thing with JS built-ins? Just so they didn't have to copy JSX? We may never know. And why are there 2 form implementations that both feel half baked? Why is it so bad to instantiate components for testing? Why does it mangle the code to support dependency injection when decorators and DI support don't even actually exist in JS even in ES2018? Why is Polyfills.js such a minefield? I could go on but really, why are so many things half assed and haphazard. It reminds me of Go...
Constant "expression changed after it was checked" errors because the data model change tracking is fundamentally broken
Repeated refactoring of HTML form interop and it still kinda sucks
Major breaking changes on nearly every upgrade that take days to do, even on our small apps.
Crappy documention. There's no usage examples for most of the library, just the Angular version of Javadoc.
Terrible bike shedding by Angular and Material teams. I'm following a bunch of issues and I've never seen one closed. I've been following some of the threads for years.
That was a nasty rant but I have plenty of things to hate about Angular. React on the other hand has a mostly clean core API and doesn't force all this baggage on you. IMO this has spawned a competitive ecosystem where the bad ideas get shaken out. Angular is stuck in the past and feels creaky compared to React development these days.
JSX is the future. It's exactly how MVC frameworks used to work, and it would be popular for templating even if the rest of React didn't exist. Change tracking with props is another. It's simple, it works. Angular change tracking errors are the segfaults of front end dev
>Constant "expression changed after it was checked" errors because the data model change tracking is fundamentally broken
Sounds like are doing something wrong. At least I can't remember that particular one from three years of Angular >=2
> Repeated refactoring of HTML form interop and it still kinda sucks
Major breaking changes on nearly every upgrade that take days to do, even on our small apps.
I did most of upgrades for over a year I think. They were mostly trivial after reading up on the changes and I don't consider myself a 10x engineer. Pro tip: Learn to use this repo: https://github.com/cexbrayat/angular-cli-diff
> Crappy documention. There's no usage examples for most of the library, just the Angular version of Javadoc.
Not perfect (internal inconsistentencies where one paragraph says "don't do this" and a couple of pages down they do exactly that).
But far far from Javafoc.
> Terrible bike shedding by Angular and Material teams. I'm following a bunch of issues and I've never seen one closed. I've been following some of the threads for years.
I don't like Material either ;-)
For everyone else:
Like always: keep it simple. Stick with the standards. Use a good ide/editor. Use Angular CLI, stick to the style suggested by that even though you don't have to use it for every small thing.
Angular does crazy things to the templates, to the point that trying to build your own UI widgets is a recipe for pain.
Template meta-language is stupid. It's just similar enough to JS that you mess up the syntax all the time and never really stop. Since it's not just JS like JSX there's not good linting support either.
Related, stupid "pet features" and hydra syndrome. Like Pipes. Why does Angular use these weird pointless things when you can do the same thing with JS built-ins? Just so they didn't have to copy JSX? We may never know. And why are there 2 form implementations that both feel half baked? Why is it so bad to instantiate components for testing? Why does it mangle the code to support dependency injection when decorators and DI support don't even actually exist in JS even in ES2018? Why is Polyfills.js such a minefield? I could go on but really, why are so many things half assed and haphazard. It reminds me of Go...
Constant "expression changed after it was checked" errors because the data model change tracking is fundamentally broken
Repeated refactoring of HTML form interop and it still kinda sucks
Major breaking changes on nearly every upgrade that take days to do, even on our small apps.
Crappy documention. There's no usage examples for most of the library, just the Angular version of Javadoc.
Terrible bike shedding by Angular and Material teams. I'm following a bunch of issues and I've never seen one closed. I've been following some of the threads for years.
That was a nasty rant but I have plenty of things to hate about Angular. React on the other hand has a mostly clean core API and doesn't force all this baggage on you. IMO this has spawned a competitive ecosystem where the bad ideas get shaken out. Angular is stuck in the past and feels creaky compared to React development these days.
JSX is the future. It's exactly how MVC frameworks used to work, and it would be popular for templating even if the rest of React didn't exist. Change tracking with props is another. It's simple, it works. Angular change tracking errors are the segfaults of front end dev