4 ms·
We're just finishing up porting our app from React to Vue and we're very happy with the results. I don't really understand's the author's point about GraphQL a
by Bizarro 8y ago
We're just finishing up porting our app from React to Vue and we're very happy with the results.
I don't really understand's the author's point about GraphQL and Axios. But React Router, Redux and its ecosystem of supporting libraries are issues in React development
Having state management (axios), a built-in router, "the" styling solution built into Vue is a big win for us. Single File Components (SFC) are a joy to work with.
I actually like JSX (which you can use in Vue too), and was worried about "stringy code" ala directives, but in practice it hasn't been a big deal. We also switched from Typescript to plain ES6 which is a big win in simplifying our code. I'm actually a big fan of static typing, but at the end of the day Typescript's complicated type system, typing file incompatibilities, and general fiddling around with types wasn't worth it for us.
Redux was just a nightmare for us to work with. A library on top of Redux like DVA https://github.com/dvajs/dva https://github.com/dvajs/dva would've helped, but there's a very small community there. We went to Mobx State Tree for a while, but there were a bunch of issues there too.
I'm keeping an eye on Blazor for some administrative apps in the future, but for now we're very happy with Vue.
- balfirevic 8y ago> Having state management (axios) Axios is a http client library, not state management library, you're thinking of Vuex. That being said, I don't know why the author associates Axios with React ecosystem, it's just a library you can use with any of the client frameworks.
- Bizarro 8y agoRight, I got my "library with x in the name" screwed up. I've found vuex much more pleasant to work with than straight redux. I wish Facebook would just come out with an "official stack" already and put something on top of plain Redux to make it more programmer ergonomic.