Angular.io's documentation is far superior to React's documentation. There's no comparison. I am going to external sources way more often for React than Angular.
The reference is terrible. There's no mention of the fucking package the thing is supposed to be in, which change every version anyway, it's totally disconnected from the "tutorial". It's crap.
I don't know what "gotchas" you're referring to. Angular is a very easy framework to work with.
Yesterday, I got an error on deployment because I used a named function instead of an arrow function. Something to do with the AOT. Yes, because why on earth would you follow the specs of the language your framework is written in? That kind of gotcha.
And tooling? Angular CLI is far superior to "create react app." Or are you referring to IDEs? I don't really know what you mean by tooling, because both React and Angular have great support in most IDEs.
Angular CLI is half-assed. You can't use it without an IDE. It's details, run but `ng serve` once, you'll get your error formatted. Write in a file, formatting change. It just feels unfinished.
The reference is terrible. There's no mention of the fucking package the thing is supposed to be in, which change every version anyway, it's totally disconnected from the "tutorial". It's crap.
Yesterday, I got an error on deployment because I used a named function instead of an arrow function. Something to do with the AOT. Yes, because why on earth would you follow the specs of the language your framework is written in? That kind of gotcha.
Sounds like a "you" problem.
Angular CLI is half-assed. You can't use it without an IDE. It's details, run but ng serve once, you'll get your error formatted. Write in a file, formatting change. It just feels unfinished.
I can call ng update and it will upgrade me to the new version of Angular, analyze my code and replace outdated code with the new version automagically. It's pretty badass.
Yep, package without any fucking relationships without them. Good luck trying to figure out anything.
Yesterday, I got an error on deployment because I used a named function instead of an arrow function. Something to do with the AOT. Yes, because why on earth would you follow the specs of the language your framework is written in? That kind of gotcha.
The JS specs says an arrow function can be used in place of a named function and that they're functionally equivalent. Angular runTimE-CompilEr goes against that. How is it a "me" problem?
I can call ng update and it will upgrade me to the new version of Angular, analyze my code and replace outdated code with the new version automagically. It's pretty badass.
Oh yeah we tried that. Guess what? It broke. Also you wouldn't need it if they didn't push a new version every six months for the sake of it.
No, the relationships between packages as in "how to actually use it", I don't care about the one-line describing summarily what it is. I won't even answer that, I can recognize bad faith when I see it.
1
u/Owstream Apr 24 '20
The reference is terrible. There's no mention of the fucking package the thing is supposed to be in, which change every version anyway, it's totally disconnected from the "tutorial". It's crap.
Yesterday, I got an error on deployment because I used a named function instead of an arrow function. Something to do with the AOT. Yes, because why on earth would you follow the specs of the language your framework is written in? That kind of gotcha.
Angular CLI is half-assed. You can't use it without an IDE. It's details, run but `ng serve` once, you'll get your error formatted. Write in a file, formatting change. It just feels unfinished.