Vue is good for simple things. But it do not shines for complex apps and sometime makes it even harder than it should be.
React can appears complicated when beginning, but it pays off on complex apps.
Vue.js vs. React
11–20 of 486 posts
Re: Vue.js vs. React
#12I would go with react just because it is more popular. Unless you are someone with free hand picking a technology that is more widespread (hence more in demand) is in this era the wise choice to make.
The demand for both React and Vue.js is growing tremendously. There isn't really a wrong choice to make here.
(I would also say the same goes for picking programming languages, as long as it's one of the top ~15, and you stay somewhat flexible.)
Re: Vue.js vs. React
#13How are people getting along with Vuex vs Redux?
It looks pretty clean and grokable in the examples and deals with async out of the gate -
Re: Vue.js vs. React
#14Vue is good for simple things. But it do not shines for complex apps and sometime makes it even harder than it should be. React can appears complicated when beginning, but it pays off on complex apps.
This is the impression I get, but I've not got any Vue experience to back it up so it's literally just based on first impressions.
I completely agree that React can feel like overkill for simple stuff, but really shines as the apps get more complex - complexity feels a lot more manageable.
For example, I built this in-browser Illustrator-inspired site/app using React and couldn't have imagined doing it without (in terms of making managing state and reasoning about things easy as the app grows more complex): http://f37foundry.com (the type tester on the desktop homepage, apologies for limited browser support!). Curious if you could do that sort of complex app with Vue.
Re: Vue.js vs. React
#15Vue is good for simple things. But it do not shines for complex apps and sometime makes it even harder than it should be. React can appears complicated when beginning, but it pays off on complex apps.
This is the impression I get, but I've not got any Vue experience to back it up so it's literally just based on first impressions. I completely agree that React can feel like overkill for simple stuff, but really shines as the apps get more complex - complexity feels a lot more manageable. For example, I built this in-browser Illustrator-inspired site/app using React and couldn't have imagined doing it without (in te…
what seems overkill in reactjs?
Re: Vue.js vs. React
#16Vue is good for simple things. But it do not shines for complex apps and sometime makes it even harder than it should be. React can appears complicated when beginning, but it pays off on complex apps.
People keep on saying this, but I've written complex apps with both Vue and React (using state stores) and there don't to be any apparent scaling differences. They even use the same component model (virtual DOM, props down, events up).
There are some claims that Vue uses two-way-binding which is unmaintainable, but v-model isn't true two way binding and is just syntax sugar for builtin tags: https://v1.vuejs.org/guide/forms.html With React, you would have to explicitly write the event handler/setter out, and some may prefer explicitness (but again, there's nothing stopping you from doing the same with Vue).
Vue just has some nice features (computed properties, better style scoping, etc) and different methods for inheritance/templating (but you can use ES6 classes and JSX if you want to), and like somebody else mentioned, is plug and play (yes, you can technically write React render functions without a transpiler, but do you want to?) while Vue (with the template compiler bundled) lets you write templates with HTML attributes using just a script embed.
There are a bunch of other arguments that are more nuanced (ecosystem, bus factor, etc..) but from what I've experienced, Vue is no worse at scaling than React simply because they share the same conceptual model.
Re: Vue.js vs. React
#17Vue is good for simple things. But it do not shines for complex apps and sometime makes it even harder than it should be. React can appears complicated when beginning, but it pays off on complex apps.
This is the impression I get, but I've not got any Vue experience to back it up so it's literally just based on first impressions. I completely agree that React can feel like overkill for simple stuff, but really shines as the apps get more complex - complexity feels a lot more manageable. For example, I built this in-browser Illustrator-inspired site/app using React and couldn't have imagined doing it without (in te…
What is complex about the site?
Re: Vue.js vs. React
#18Earlier quoted context omitted.
This is the impression I get, but I've not got any Vue experience to back it up so it's literally just based on first impressions. I completely agree that React can feel like overkill for simple stuff, but really shines as the apps get more complex - complexity feels a lot more manageable. For example, I built this in-browser Illustrator-inspired site/app using React and couldn't have imagined doing it without (in te…
what seems overkill in reactjs?
I mean for the simple use cases like adding some validation to a form or a simple widget on a site. But in my experience, these projects usually grow to the point where you are glad you went with React. Personally I'm a huge fan and build things with it I couldn't have imagined doing a few years ago, so I hope all this patent stuff gets resolved/blows over.
Re: Vue.js vs. React
#19I've used both. What makes me pick Vue in the end is the fact that there is no compiler needed, no jsx and all the non-sense that goes with that.
If you want a full blown huge application to last years, then go Angular... Although who knows if Angular will be there in 5 or so years.
There is no perfect library/framework but I love Vue because Vue does exactly what it says on the tin.
Re: Vue.js vs. React
#20My #1: download vue(.min).js and you are ready to go. No packagemanager, bundler and what not needed.
You can do the same with react. Unfortunately with either library you are going to want it for any serious project.
Exactly. I would rather see the community focusing on a standard workflow like ember-cli and angular-cli.