Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Congratulations, but to me React is like Rust. Something I always wanted to get into but found better alternatives. In the react case Vue wins for me and in the Rust case it's Go.

I really tried, time and time again to like it and write something with it, but Vue just offers the better libraries. Altough with the recent 2 to 3 upgrade and pinia instead of vuex I'm starting to get dissatisfied with the "no single proper way" of Vue. Vuex-orm being the best frontend REST wired ORM, nothing comes close to ease of use and setup. Meanwhile react has what? Complicated redux, or is that even a thing anymore? Idk, which I would. Redux the boilerplate abomination. That's exactly what drove me away from Angular. But I'm starting to rant again. And react has even more of the "not a single proper way". Yeah I know, nextjs the magic bullet, but what if you don't agree with pretty much everything about it, starting with routing.



I've worked both on large Vue and react projects. Wouldn't pick myself Vue ever if I have the choice.

Vue is certainly easier to learn, and comes with a lot of oficial libraries such as vuex, Vue router etc. But that's all about it.

The Vue 2 to 3 transition is a big fuck up, python level. One of the companies I've worked for will never be able to migrate to Vue 3, because they cannot afford to stop product development and they also have a ton of external dependencies that are mostly abandoned.

The integration with typescript, even in Vue 3 is still not as good as it is for react. This is critical for large projects, and to have proper ide autocomopletion, etc.

Then the ecosystem....it is a lot smaller than the React ecosystem.

Then the "meta frameworks". Next.js is infinitely better and better managed than Nuxt, which went full rewrite and again, from my point of view that's a big fuck up.

And finally, I have absolutely nothing against other languages (even English is not my native language) but I got really tired of finding myself debugging problems and ending up in issues, forums or readmes in languages that are not English (mostly Chinese).

React has its drawbacks, but I prefer those by a far amount to the drawbacks of using Vue.


> to me React is like Rust. Something I always wanted to get into but found better alternatives.

That's funny. To me it's the other way. I love both React and Rust. Vue and Go both seem like tools that get halfway to the benefits of React/Rust and would be good choices if React and Rust weren't available.

> Meanwhile react has what? Complicated redux, or is that even a thing anymore? Idk, which I would. Redux the boilerplate abomination.

There is now redux-toolkit, an official part of the redux project that provides a standard convention and helper within redux that reduces that boilerplate. There's also mobX which is more like Vue's state management. Both are well supported.


FWIW, our official Redux Toolkit package solved the "boilerplate" concerns, including our new RTK Query data fetching API.

If you're happy with Vue, great! If you do get a chance, though, please take a look at the Redux docs tutorials to see how we teach writing "modern Redux" code today:

https://redux.js.org/tutorials/essentials/part-2-app-structu...


You’ve mentioned two of my favourite technologies :)

In case you want to try rust and react together:

https://github.com/Wulf/create-rust-app


If you are looking for api client library that has automatic updates propagation in the UI, condider giving Appollo Client and GraphQL a try.

…but I am finding lack of client library for React implementing eg. Open API protocol hard to believe. Is that true?


React and OpenAPI are orthogonal things. You'd build a JavaScript/TypeScript library for talking to an API, not a React one.

(Generally, though it adds some friction unless you have HTTP servers with libraries to help you out, I prefer this approach whenever possible to GraphQL. Mostly because relying on frontend folks to inflict terrible damage to databases via wild abuse of resolvers is not my cup of tea, but as GraphQL tools become smarter I'm coming around on this a bit.)


Well, yeah, but OP claims doing REST client with react is something hard.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: