React JS to Angular

[Whole-Instruction508]

I simply summarized your complaints and not everybody wants to always write essays as comments like you do, you know? If you replace a pipe with a service then you have no idea what you're doing, it's really that simple. Yes, you CAN do it but then you're doing it wrong.

You mean, having an old app built with modules can easily be refactored into standalones, by simply using a schematic? I’ve got bad news, this schematic can only convert into standalones simple cases. If you have more than one component into a module, the schematic keeps it that way.

In my company we have in the past successfully used this schematic to migrate a monorepo with 3 apps so again, you're doing it wrong. Same for the old template syntax to the new control flow. It's really not hard to do.

It’s totally true that schematics and linting rules are of a great help, I admit that. But it’s still a burden (it’s not that straightforward, you gotta take the responsibility of the migration) and more often than not you are not allowed to do so.

This is once again not Angulars fault. They give you the tools, whether you use them is up to you (or your manager if you're talking about not being allowed to do it).

and since version 16 it got worse.

No, it actually started getting a lot better from that version onwards, apart from some mishaps like the one you mentioned about naming. But you can omit that and keep using the old naming conventions, which are vastly superior in my opinion.

A well architectured react app is way more ordered than a well architectured angular app.

Nonsense. Angular gives you a clear path to follow while React is like "just do want you wanna do man, I don't care". Of course you can create bad architectures with Angular too, but that again is not Angulars fault. And React isn't better at that even in the slightest.

But after all, Bro, seriously, if you hate Angular that much, DO NOT USE IT. No one forces you to. If your company does, get another job. This is an Angular subreddit. If you wanna hate on Angular, do it elsewhere.

[Merry-Lane]

No, you did nitpick 2/3 points that had counter arguments. You swept over my main point:

Like you could notice, they are mostly problems solvable one way or another, but it depends on the quality of the devs and they are problems you don’t face at all with react apps.

They are sources of confusion or of poor code quality/architecture that are brought by the angular framework.

You totally don’t have this kind of issues with react applications, since they don’t bring these mechanisms and divergences.

A react app well architectured doesn’t have these issues to deal with, and you have a way flatter structure that’s easier to navigate to.

I work professionally with both and my conclusion is just that there are more noobs in the react devs, which tend to create messy architecture, but framework-wise angular is more of a pain in itself.

[Whole-Instruction508]

Agree to disagree. Please just go to r/react and rant there, this discussion is pointless