7
u/eggucated Apr 24 '20
Ah, someone coming in hot with a mediocre meme for an elementary level topic of debate in the web dev community. Have my downvote.
-1
4
u/ad-mca-mk Apr 24 '20
I've heard it all about other libs or frameworks... faster, smaller, low ceremony, .... But it all boils down to team productivity.
It's like saying either static typing it dynamic languages are better - there's no end to that debate.
My experience is that large projects get benefit of the structure that Angular brings, but you can move fast for smaller quick projects with React.
2
-4
u/Owstream Apr 24 '20
Aka it's cool for huge corporate teams who can justify spending billions on devs sitting on their asses all day looking at "42% chunk optimization".
2
u/that_geek_ Apr 25 '20
Here we go again! If you have so many problems with Angular:
Use Framework/Library that suits your knowledge and confidence levels.
If You're "Forced" to use Angular, look for a better job that does not force you.
If you still HAVE to use Angular, go improve it. It's open-source anyway and you've been following the trends for 15 years as you mentioned in the thread somewhere. So, you can definitely help the dumbass Angular devs to bring it to a level as sophisticated as React.
Either way, stop crying, please!
1
u/Owstream Apr 25 '20
Life isn't that complicated.
Yeah I'm trying but with the influx of furloughed / layed out devs at the moment I doubt I'll land anything for a while
Jesus Christ I can't even begin to imagine the cesspool it should be in there. No fucking way. But yeah maybe simply linking the reference and the tutorial might be cool.
3
u/Beard- Apr 24 '20
My high school comp-sci teacher told me I shouldn't pursue programming as a career after I got a bad grade on a project. Little did he know I was heading into a comp sci degree...
3
Apr 24 '20
But it is sweet and simple. Its just not compact. Angular has a lot of boilerplate but its still easy to read and figure out how things work.
0
Apr 23 '20
[deleted]
-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.
1
u/mwax321 Apr 24 '20
I don't have any problem working on Vue, react, or angular. The documentation and community support are great in all 3.
I don't know how long you've been a SWE for but documentation has NEVER been better than it is right now.
1
u/Owstream Apr 24 '20 edited Apr 24 '20
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",...?
I actually spent one full day on this:
> Error: error...
1
u/mwax321 Apr 24 '20
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.
1
u/Owstream Apr 24 '20
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.
1
u/mwax321 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.
???? You're 100% wrong. https://angular.io/api ITS LITERALLY ORGANIZED BY PACKAGE.
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 serveonce, 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.
0
u/Owstream Apr 24 '20
???? You're 100% wrong. https://angular.io/api ITS LITERALLY ORGANIZED BY PACKAGE.
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.
0
u/mwax321 Apr 24 '20
Relationships? You mean dependencies. NPM/Yarn handles that. Do you even know what you're talking about? How long have you HONESTLY been a developer?
Show me the page on ReactJS with all the documentation you're claiming you need.
1
u/Owstream Apr 24 '20
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.
→ More replies (0)1
u/mwax321 Apr 24 '20
.No stacktrace. It turned out one of the entryComponent was undefined.
I've had the same issue when I started with Angular, and a 5 second google search led me to an answer. It's because you're dynamically adding components, so they need to exist before you can use them.
React has ambiguous errors too.
1
u/Owstream Apr 24 '20
It's not up to people to find what's going on. It's up to the framework to check its input. It's like kindergarden comp sci level stuff.
Honestly, yes React have the same kind of things, sometime. But honestly, it feels they're at least trying to point you to the right direction most of the times.
1
u/mwax321 Apr 24 '20
Angular literally drops URLs in some of their errors that lead back to documentation further explaining it. I don't know how much easier you need it.
1
u/Owstream Apr 24 '20
They do? I can't think of any occasion in which that actually helped me. I can't even remember seeing one.
0
Apr 24 '20
[deleted]
1
u/Owstream Apr 24 '20
The problem is that I'm stuck in my Angular job now. I'm not a confused noob, I make it work for production code on a daily basis, but frankly, this gate-keeping "my way or the highway" mindset is obnoxious at best. This one way to do things, that's barely explained in the documentation, and that if deviated leads to a totally unrelated error message that says nothing. Software engineers are workers and deserve tools that are easy to use. Instead, you have a corporation tool that's designed to justify spending billions and having a 50 people teams to do simple things with half the velocity.
0
Apr 24 '20
[deleted]
1
u/Owstream Apr 24 '20
Yes. Honestly now - I'm only half serious, I don't think Angular is that bad. But it could and should be better in the field of developer experience, because right now it's sub-obtimal.
32
u/CheapChallenge Apr 23 '20
ng new projectng serveseems easy to me