6 ms·
This is why despite trying Vue first and liking it, after learning React, I would always use it in the future. Vue really requires you invest in its ecosystem
by koboll 8y ago
This is why despite trying Vue first and liking it, after learning React, I would always use it in the future.
Vue really requires you invest in its ecosystem a lot more to structure your entire frontend (and Nuxt even more so), whereas React feels and operates much more strictly as a JS library.
The basic benefit of Vue is that it comes with much of the React boilerplate already abstracted away behind syntactic sugar. But once you learn to do that yourself with React, it's no slower to start building. It just takes a longer learning curve to get to that point.
- burlesona 8y agoAfter using each in production for about two years I came to the opposite conclusion. For me the React experience includes tons of bikeshedding over which accessories (routing, state management, etc) to pair it with and how to wire those up. The Vue experience started simple and scaled up nicely as we reached the point that we needed more stuff, since there’s an official library for basically everything and it all works very nicely together. It’s pretty subjective I guess but interesting how different development experiences can be.
- bhj 8y ago> For me the React experience includes tons of bikeshedding over which accessories (routing, state management, etc) to pair it with and how to wire those up. This is React's biggest strength IMO, that it doesn't handle routing, state, etc. It just makes your UI a function of state. How an app needs to manage state can vary wildly, but it's all the same to React.