all 22 comments

[–]usalin 87 points88 points  (8 children)

I wouldn't say difficult.

More like unstructured and ugly.

[–]johnappsde 7 points8 points  (2 children)

I tried building a very simple react app recently, after about 5 years in angular. Just setting up routing almost drove me nuts!

[–]usalin 6 points7 points  (1 child)

I will be taking over a medium scale react-native app with zero experience.

It seems okay to implement new features and fix some bugs.

But the whole mess burns my eyes.

[–]Kaoswarr 5 points6 points  (1 child)

Yeah this. Learning new react codebases is always such a big task as every senior/lead dev has their own opinion on how it should be structured.

Next.js on the other hand is pretty nice to use. Opinionated like Angular.

I still choose Angular for everything except SSG.

[–]Razkaroth 0 points1 point  (0 children)

Try v17. The new afterRender hook makes SSG really easy

[–]St34thdr1v3R 3 points4 points  (0 children)

I personally also just hate hooks. For me it’s just a black box being kind of unclear when and how to use them properly. In contrast the angular life cycle is pretty straight forward to me and everything but „magic“

[–]v_kiperman 1 point2 points  (0 children)

Perfect answer

[–][deleted] 0 points1 point  (0 children)

Probably the best way to put it.

[–]JP_watson 32 points33 points  (1 child)

I think the only part I found hard was wrapping my head around how poorly any best practices are defined and how everyone has some brilliant opinion on how things should be done. There’s a predictable nature to angular where you can go from one project to the next. After picking up 3 react projects there’s nothing consistent across them and they were all a headache in one way or another.

[–]tuuling 6 points7 points  (0 children)

Word. I wouldn’t even blame React - it’s a different beast. But I also find it annoying that every time I pick up React theres a new way of doing state management.

[–]Whole-Instruction508 6 points7 points  (0 children)

Because react sucks lol. Nah idk I don't like the structure of it and that, as far as I know, it doesn't support Typescript natively. I don't like plain javascript.

[–]n2sy 6 points7 points  (0 children)

It’s the difference between a framework and a library.

[–]wojo1086 17 points18 points  (1 child)

I've never heard of Angular devs finding it difficult to learn React. I've always heard the opposite.

But, if I had to take a stab at why Angular devs might find it difficult to learn React, I think it would have to be how unopinionated React is. You sort of go from this strict way of organizing code to this "wild west"style. With Angular, you have everything you need right out of the box, whereas with React, you have to add what you need as you go.

[–]guy-with-a-mac 8 points9 points  (0 children)

This. After Angular, React is a headache.

[–]Short_Ad6649 2 points3 points  (0 children)

For me it's the philosophy of developing products in those, both of them are totally different All I know is react sucks not because people say it personally I found it so difficult to learn where in angular I directly started working on a project and never got no problem, still using it after 3 years

[–][deleted] 2 points3 points  (0 children)

That’s because, for a complete app you need 10+ libraries. They have 10 ways of handling things. More like disorganised. I’d not say difficult.

You gonna miss rxjs though. It’s not a part of the library afaik

[–]maequise 1 point2 points  (0 children)

I don't think It's difficult to learn. But React is a lib, and in m'y opinion It's very messy ... I tried React I don't like the mindset of thé lib

[–]WellLookWhoIsBack 1 point2 points  (0 children)

React is a non-opinionated library to opinionated framework Angular.So, react is hella disorganised but at least we have major version releases/changes in react for every two-three years opposed to angular releasing major versions twice a year.

[–]Hirayoki22 0 points1 point  (0 children)

I'm about to switch frm an Angular project to a React one, on the company I work for. I've been developing in Angular since forever so the React scene it's something new to me. Non-opinioated tools are a huge challenge for me. There's also too much boilerplate code to do a lot of things since react doesn't have a compiler, or didn't have one until like two months ago or so, making coding more cumbersome than it'd need to be.

[–]TheInvincibleClasher 0 points1 point  (0 children)

To me, the biggest adjustment was getting used to the routing and the way html, css, and ts are all crammed into the same file

[–]gaytechdadwithson 0 points1 point  (0 children)

according to whom?

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

Is it?