3 ms·
They're pretty similar. I prefer React because the JavaScript-first approach is much better for large applications. It leads to a smaller API while simultaneous
by ng12 7y ago
They're pretty similar. I prefer React because the JavaScript-first approach is much better for large applications. It leads to a smaller API while simultaneously giving you more control over how things work. Also Vue has a lot more magic to it which you might care about on a large project.
The use case I recommend Vue for is when you just want a quick drop-in solution. For any serious development I stick with React.
- bt3 7y agoFor any serious development I stick with React. Isn't this a bit disingenuous given Vue's usage in true, scalable production capacities? I'm not the expert but companies like Netflix, Adobe, and GitLab have Vue deployed at scale. Since when was "quick" synonymous with "not sufficient for serious development"?
- ng12 7y agoTo my understanding the biggest reason GitLab chose Vue was because they were able to easily mix it in with their existing stack. That's part of what I was referring to by "drop-in". You can do the same with React but it's more heavyweight unless you plan on porting the lion's share of your app to React. As for the others I'm not sure what they're using Vue for specifically and can't really speak to the technical reasoning behind it. I'm not saying that you can't do serious development in Vue but rather that all else equal I will guide teams to adopt React, mostly for the better developer ergonomics.
- manigandham 7y agoThere's nothing trivial about being "drop-in". Usually these are complex apps running on traditional web frameworks and/or use server-side rendered pages where Vue excels in adding front-end interactivity because it uses HTML templates by default (with that HTML coming from the server).