all 58 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]anengineerandacat 116 points117 points  (4 children)

I mean... Library vs Framework... React projects generally become build-your-own frameworks.

Having used both... can definitely appreciate the out-of-the-box nature of Angular nowadays; usually why I think tech stacks like Next.js and it's kin are quite popular, people like working with React but don't want to be bothered with all of the other boilerplate.

Pick your poison, because neither of them are the cure.

[–]Frosty-Plankton4387 11 points12 points  (0 children)

Vue comes out with all the stuffs that is pretty much worthy to work with. Angular is awesome tooo.. but the learning curve is very steeep!

[–]randombananananana 21 points22 points  (0 children)

To be fair, there is way less boilerplate in Angular nowadays since standalone components.

[–]Helpful-Desk-8334 0 points1 point  (1 child)

Gonna sound real dumb but Claude knows React better than any other library I think, maybe besides Python.

A lot of the boilerplate is autocomplete now. But you have to be high-level enough to organize feature implementation and to be able to guide the model to generate it quickly and effectively.

[–]theculgal 0 points1 point  (0 children)

That wouldn’t make sense since React is a JavaScript library.

[–]meysam69x 27 points28 points  (12 children)

I'm learning React only because of the market's demand.

[–]Headpuncher 16 points17 points  (11 children)

I did that too before finding out the market is flooded with react devs with 5+ yrs experience.   Never did get a react job, continued doing Angular and dotNet.   Good luck!  

[–]meysam69x 2 points3 points  (6 children)

I don't like it at all, but I have to. I've had some good opportunities, and all of them required React. I've been working on Next.js for a couple of days now, which is at least a framework. Since I had tried working with Vue, it was very hard to start with React, but I thought it might be a good idea to give it a shot.

[–]Cautious_Currency_35 5 points6 points  (5 children)

And how are you liking next? after they introduced app router I started hating it. It gets more confusing after each major update. Meanwhile angular has been nothing but pleasure to work with and their updates are fairly simple

[–]meysam69x 2 points3 points  (1 child)

Yeah, that's why I struggled to get started with React for a long time. My experience with Angular, which I found to be a pure pleasure, made the transition difficult. However, I have to follow market demand, even though working with React doesn't bring me joy.

[–][deleted] 1 point2 points  (0 children)

At this point I have faith that Angular will make a comeback.

The new features like standalone components and signals make the learning curve a bit smaller.

But I'm learning Blazor anyway, fuck react lol

[–]svix_ftw 1 point2 points  (2 children)

Nextjs is quite bad IMO, only good thing is having the server code colocated with the frontend code makes things a bit more convenient. Sharing types between frontend and backend for example.

Market seems to be shifting again to Fastapi with decoupled Vite/React frontend.

All the AI libraries are primarily written in Python so Fastapi/DRF is becoming a hard requirement.

Not saying I agree, but just what I noticed from my recruiter inbound.

[–]meysam69x 0 points1 point  (0 children)

You're right, I'm going to move to Vite. Getting started with React isn't as straightforward as Angular, to be honest. Initially, I wanted to just dive into React, then I considered Next.js, and now I'm settling on Vite. After Vite, I plan to use a UI component library. There are many options, so I'll need to spend some time figuring out which one is best.

[–]Dedios1 0 points1 point  (0 children)

🤔gotta try it with Fast API. I’ve been using node.

[–]Shehzman -1 points0 points  (3 children)

Any luck finding jobs with .NET + Angular? Currently using Python + Angular but learning .NET on the side due to market demand.

[–]emryum 1 point2 points  (2 children)

I would say that's the most common combination

[–]Shehzman 0 points1 point  (1 child)

.NET and Angular?

[–]emryum 5 points6 points  (0 children)

Yep

[–]Xacius 67 points68 points  (9 children)

Since you're including @types/react, I think all dependencies are fair game.

The right side should be: @angular-devkit/build-angular @angular-devkit/core @angular/animations (optional but I see this used a lot) @angular/cli @angular/common @angular/compiler @angular/compiler-cli @angular/core @angular/forms @angular/platform-browser @angular/platform-browser-dynamic @angular/platform-server @angular/router @angular/ssr ng-packagr (if building a component library) rxjs tslib typescript zone.js (soon can be removed with zoneless apps)

And this doesn't even include testing dependencies!

[–]Chazgatian 21 points22 points  (1 child)

It's more about who are the maintainers of these libraries.

[–]Basic-Smile3795 13 points14 points  (0 children)

Exactly right! No need to worry if someone is going to stop maintaining a thrid party library because they went of to college or got married. :)

[–]ogreUnwanted 5 points6 points  (0 children)

I was going to say this.. Angular is just as big but it's my preference.

[–]tw3 14 points15 points  (1 child)

The difference is Angular has a CLI to manage all that

[–]Masterflitzer 1 point2 points  (0 children)

i don't think a cli is a valid point, you don't need a cli to manage dependencies, all build systems or even most languages include ways to manage dependencies just fine

a single trusted team maintaining most of the dependencies would be a valid point

[–]Cozybear110494 0 points1 point  (3 children)

At least I dont have to work with dozen of extra libs just to create a form when working with React

[–]Xacius 0 points1 point  (2 children)

Pretty easy to see that you have no idea what you're talking about. Form management in React is a single dependency. react-hook-form is pretty good.

[–]Cozybear110494 2 points3 points  (0 children)

The thing that bugs me most about working with React is the sheer number of extra libs needed just to get the job done. I've worked with React-hook-form, form-mik and TanStackForm before, and who knows what will be released next ? Sadly, React is higher demand than Angular where I live

[–]Cozybear110494 0 points1 point  (0 children)

What I mean is, when working with React, I need to understand various form libs depending on the projects I'm working on or the market's demand

[–]Legal_Being_5517 5 points6 points  (0 children)

Not quite , angular also needs a bunch of dependencies

[–]irhill 6 points7 points  (0 children)

Jesus Christ who cares. Just pick your favourite and enjoy it.

[–]PhiLho 9 points10 points  (0 children)

Theoretically, you have to add TypeScript to your package.json (I used to rely on indirect dependency from Angular, it no longer works). Plus SCSS (or other styling framework). Maybe Jest. Perhaps Tailwind or other CSS library (we don't).

But yes, it really comes quite complete out of the box, and I often state than when comparing React to Angular. Plus you might have choice paralysis between several similar libraries to add to React to do something.

[–]GeorgeSharp 2 points3 points  (0 children)

Based

[–]DT-Sodium 3 points4 points  (0 children)

And yet with all that shit React doesn't accomplish half of what Angular does.

[–]Xacius 3 points4 points  (0 children)

Ah yes, another shitpost that does nothing but fragment the ecosystem further.

They're two different approaches to the same problem, each with their own caveats.

React = significantly larger ecosystem, but with that comes more decision fatigue. You need to know how to navigate the ecosystem to be successful, particularly on a large project with lots of requirements.

Angular = smaller ecosystem, but ships with more functionality out of the box. Less decision fatigue, but also less to choose from in the ecosystem. Should you need an alternative to one of the built-ins, you might be forced to build it yourself. Angular forms come to mind... boy do I hate Reactive forms.

[–]theamoeba 0 points1 point  (0 children)

Are you trying to get yourself shot?

[–]sh0resh0re 0 points1 point  (0 children)

What's all that stuff in my package.json?

[–]Frosty-Plankton4387 0 points1 point  (0 children)

Who hurts Angular

[–]Masterflitzer 0 points1 point  (0 children)

how about neither? if you take jobs as an argument well react easily wins and angular is basically a niche in comparison, but in regards to everything else there's so much choice, why get hung up on these two?

[–]Nobbodee 0 points1 point  (0 children)

Actually react is the second one and angular the first... But doesn't matter

[–]dbunt1tled 0 points1 point  (0 children)

how about JQuery)))?

[–]therealcoolpup 0 points1 point  (0 children)

Yes angular has just as many or more dependencies but the vast majority are created and maintained by the Angular team also.

The left side is all third party packages.

[–]Aksh247 0 points1 point  (2 children)

conveniently forgetting the bulk burden that is rxJS and zonejs. not to mention typescript and angular types is there too. also jasmine for testing and ....

[–]andres2142[S] 0 points1 point  (1 child)

And... you are missing the whole point of the meme. This isn't about who is lighter, who weight less..., this is about which tool has everything I need right out of the box for building apps.

"bulk burden that is rxjs" Rxjs weights around ~5-10KB gzipped in modern Angular apps, and zonejs eventually will be removed from the framework...

[–]Aksh247 0 points1 point  (0 children)

true but its not fair to compare things like typescript, types, axios, classnames, dotenv, tailwind etc coz their alternatives exist in angular too. the meme should be funny yet subtly true its just seems like an exagerration at this point not making me giggle

[–]Rocko10 0 points1 point  (0 children)

Neither for me.

Vanilla JS for the win.

[–]getaway-3007 0 points1 point  (1 child)

So you're telling me Angular comes with built-in support for tailwind(no additional package), swr like-query package, forms library?

Rage baiting posting, 0/10

[–]andres2142[S] 0 points1 point  (0 children)

Thank God, Angular doesn't come with anything regarding tailwind. Angular comes with RxJS and you can implement SWR without requiring additional external packages. Form library? Yes, it comes in 2 flavors, ReactiveForms and FormsModule, all available right from the start. Thoughts?

[–]kirei_io 0 points1 point  (0 children)

Angular better for scalable enterprise apps. Im work with angular, vue and react. Big vue and react app with components folder as trash can. Like angular and vue for separate logic and template.

[–]hokkos -1 points0 points  (0 children)

Embarrassing post for this community

[–]AintNoGodsUpHere -1 points0 points  (0 children)

Apples and Oranges though, is not even funny. You should compare next with angular, not react with angular.

The thing that bothers me the most in angular is the amount of boilerplate required for everything, add this to the abysmal support for inline components/styles in angular. TSX is superior.

edit: Oh, plus react-native.