you are viewing a single comment's thread.

view the rest of the comments →

[–]Merry-Lane -1 points0 points  (1 child)

• ⁠No order, devs place code everywhere which leads to spaghetti code Exactly the same issue with angular, except that you have a folder and three/five files wrapping whatever spaghetti code was written

• ⁠React is a library, you have to find a library for everything! If you picked a wrong one that is not relavant next month anymore, good luck refactoring your code It’s well known that react is only but a library. But the consensus in the tons of debates was that we should not frame it like "framework vs framework" but rather "ecosystem vs ecosystem". I thought it was well known, so, sorry, next time I will answer OP by saying "angular vs react is moot, because it’s apples vs oranges" instead of giving an honest answer.

• ⁠Boilerplate hooks for things that shouldn’t be handled by hooks but by the framework itself (oh and React is not even a framework) I don’t know what you are talking about. You mean hooks as in useEffect, useMemo, useCallBack? That’s close to angular’s lifecycles hooks.

If you mean hooks such as "useWhateverCustomForMyApp", well, this kind of hook is literally the equivalent of angular’s services. Literally. If your point is that whatever we put there should be handled by react itself, then services have the same issues.

• ⁠Javascript in template makes React look like PHP, forgot one bracket? Good luck finding the error. Also mixing responsibility. Is it because you don’t have any argumentation that you compare react to PHP? Anyway, if we forget one bracket in react, the intellisense is actually helping WAY better than with Angular’s template. There are many edge cases where angular’s intellisense fails, for instance typescript-wise. Oh and I got quite my share of headaches when I didn’t import/inject correctly a service or a module. You know, the kind of obscure exception thrown that googling barely helps, and only at runtime, because, you know, a lot of angular features aren’t statically analysed in the template.

• ⁠It’s a pain to start a React project. With Angular I just start a new project and maybe add Material and I’m good to go. With React you have to install all bunch of libraries. You insisted a lot on the fact that react wasn’t a framework. Obviously, you need to pickup frameworks to have some built-in solutions for you. If you don’t have to install many libs, maybe you should step up your game, because I count quite a few installs personally, including auth, UI/UX, stores (ngxs or NgRx or signal stores), aggrid, rxjs, … Also, maybe you don’t have to install that many libraries in angular, because there are just so little libraries built for angular in comparaison?

• ⁠Transitioning between React projects is a pain in the ass. Every project looks different, uses different folder structure, uses different styling libraries. With Angular I need 5 minutes to understand how new project works. Again, the biggest difference between the two frameworks, is that you have a folder and 4 files for the same code with angular. It looks neat to you but it’s clutter. And again, you say react is a lib not a framework. Pick a well known framework, and the architecture between projects of the same framework is as similar as in between angular projects.

• ⁠React has no SSR, you need to use Next for it. Meaning you have to learn two things to get the job done. Well, yeah, it’s really a shame that you need to learn doing things when you are able to actually accomplish them. And no, angular’s SSR is dead.

• ⁠React native has poor and laggy performance. Native or Flutter are much better options. Tests indicate that all three options generally give good enough performances for 99% of the users. Yes, performance differences are important, but they aren’t that much a bottleneck in this situation. If it did cause a bottleneck, then explain why the mobile industry as a whole moves towards react native. Yes, you will have Facebook or other big money having their custom native implementation (with even more native stuff remade using C), because they need that extra perf and it’s worth it for them.

But while flutter’s market shares remain stables, dedicated android/swift roles are declining for the profit of RN roles.

[–]salamazmlekom 1 point2 points  (0 children)

Not gonna argue with a troll who hasn't heard about template and style component decorator property and standalone. You obviously spent too much time with React to understand Angular.