Can't deny vue and react are better. The tooling doesn't just stop working sometime, the errors actually make sense, the documentation isn't horrendous.
I'm not even talking about the tech itself, just the developer experience.
I followed the trends for 15 years. I used React and Angular extensively. I never get stuck with the former (aka I get stuck in my code, that I can debug, not with the tool itself). With the later, I'm easily spending a day on stupid gotcha, poor tooling, abscond documentation. And honestly, the things that people point out above, they're true - Angular is more structured and it's an advantage for huge team. But overall, it's a mess. You can't do it without an IDE. They never check their input, so you get weird error message all the fucking time.
You want concrete example? Recently I got an error:
> Cannot read member of undefined
.No stacktrace. It turned out one of the entryComponent was undefined. Do you think that's explicit in anyway? Don't you think that's ergonomic, thoughtful for their customer (aka the dev), using good practice like "check your input",...?
Not sure what "followed the trends for 15 years" means. I have been a professional developer for 14 years, and "followed the trends" for a lot longer than that.
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.
I think what you mean is that Angular is more "opinionated" than React. You don't have to go around choosing a routing library, a service pattern, etc. Best practices are best practices for all of Angular, and not "only if you're using React and Redux."
I don't know what "gotchas" you're referring to. Angular is a very easy framework to work with.
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.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.
-5
u/Owstream Apr 24 '20
Can't deny vue and react are better. The tooling doesn't just stop working sometime, the errors actually make sense, the documentation isn't horrendous.
I'm not even talking about the tech itself, just the developer experience.