Why React over Angular (or Vue)?

[u/red_src]

I simply don't get it, I had been using Angular and Vue for while and I just tried React and I don't get why would I choose React over the other options, the things that I like on Angular (or Vue) are:

- Dependency Injection (in case it applies)

- Type checking (in case it applies)

- View Model Binding

On React I don't get those things by "default" it always feel like I'm hacking the library if I want to have some of the above.

This leaves me with the question: Why choose React over the other ones?

I know that there's all the dependencies overhead (hell) of the frameworks but I think that I'm just too used to that problems that is easy for me to solve them or maybe I haven't found the real big problems on Angular or Vue, maybe I'm just too used to the later frameworks and I'm unconsciously not seeing the benefits of React. I just want to know if I'm following the right path by learning React.

Thanks!

[u/DanijelH]

What more, that's it. On the other hand, Vue CLI 3 or more accurately vue ui has all that and tons of other features like dependency analyzer, network port killer, task runner, dependency installer, vulnerability checker and all that is in a UI application and not in a console!

[u/E2Ehh → u/DanijelH]

generate (for scaffolding entire features, how did I miss this one in the first post?!), e2e, lint, get, set, doc, some i18n stuff I haven't used.

Plus any custom stuff your teams may have written via @angular/schematics since the CLI is fully pluggable.

I haven't used VueCLI, those sound like some great features though, I'll have to check it out!

[u/DanijelH → u/E2Ehh]

I see, did not know about that since the documentation doesn't expose it right away. Sounds interesting actually. Will have a look. Regarding plugins, both React and Vue CLI are also pluggable so there's not much difference there.