7 ms·

We switched from React to Vue.js recently and we are never going back. Our team couldn't be happier as our productivity dramatically improved and I can tell you

We switched from React to Vue.js recently and we are never going back. Our team couldn't be happier as our productivity dramatically improved and I can tell you it's not even funny. First, to answer OP's question, well the question is a little weird because i'd say that jquery supplements your vue.js app and makes it even more powerful. For instance, jquery provides methods like $.post() and $.get() along with a wide array of utility functions that you would typically use in your vue.js app. But if you were comparing Vue.js to other frameworks like React, I'd say it's not only easier, it's a lot more fun to use and elegant (the same way jquery did for DOM several years ago). I would say always bet on elegance! There is a horde of React developers who probably invested way too much time for them to move to anything else but my advice to them is once you go vue.js, you are probably not going to wanna go back, and hopefully that is a good thing. React can be fun to learn in the beginning but over time it does cause a lot of fatigue when you need it to do a little more, which can overcomplicate your app rather quickly. So in my mind, I wouldn't be surprised if vue.js takes the lead over React anytime soon.

cormacrelf 10y ago
I get the feeling that React with the Redux/Flux architecture scales to Facebook-level complexity a bit better than Vue. Vue feels kinda like if you made plain React with setState a lot easier to use. The complete separation of presentation and state with flux is a lot of work but starts to pay off when your data is used in many places and you can just connect any piece to the same global state and keep consistency. Or when you can make writing API interactions really easy with one middleware and from there your requests are done declaratively with actions. I wonder what it's like to use Vue with Redux! Probably a bit weird given the two-way binding, where Redux is all about one-way binding and cycling every change through a global state transition. At first glance (revue, vue-redux) this seems awkward. How does your team accomplish the stuff you would otherwise do with Redux? How do you do AJAX and how do you propagate that around? I suppose it's just like regular MVVM, all pretty isolated.
- wishinghand 10y ago
  Just FYI, Vuex is the first party answer for a Redux solution for Vue.
- unculture 10y ago
  You can totally use Redux, but conceptually Vuex is so similar that you may as well use that. Also, Vue doesn't really have two way binding, just the v-model directive that is syntax sugar for handling an event to update component state.
- Etheryte 10y ago
  Redux is just a fancy PubSub, you don't need it to scale. The main thing Redux got right was jumping on the React hype train. Don't get me wrong, I write React apps with Redux myself, but Redux is far from being a mandatory component.
- jaequery 10y ago
  I'm pretty sure 99.999% of websites don't require Facebook complexity. And even if you do require it, I don't see why Vue.js can't handle what Facebook does.
wishinghand 10y ago
Vue-router gets you all of the CRUD operations if that's all you're using jquery for.
- patrickdavey 10y ago
  Just checking, did you mean vue-router .. or did you mean vue-resource[0]. I've only played with vue a bit so I could be missing something. [0]https://github.com/vuejs/vue-resource https://github.com/vuejs/vue-resource
  - wishinghand 10y ago
    I totally meant Vue-resource, but for some reason I keep mixing the two up when I speak or post about them.
BrandoElFollito 10y ago
Would you mind elaborating a bit on "a wide array of utility functions that you would typically use in your vue.js app."? I am an amateur developer (home projects) and started to use Vue which I find excellent. I had the idea, though, that using Vue and jQuery at the same time is not correct (= technically it works but it is not recommended as Vue is supposed to do the jQuery things. If you use jQuery then your Vue design is wrong. Again, this was my understanding). Except for AJAX where I use qwest anyway.
- AOsborn 10y ago
  You have this pretty much right. You want to avoid overlapping jQuery and Vue for areas both cover such as event binding and DOM manipulation. This should be left to Vue. jQuery provides a number of other functions but AJAX is the major part of this. See https://api.jquery.com/category/utilities/ https://api.jquery.com/category/utilities/ If you already have a solution for AJAX, you might be interested in looking into a more generic library to complement Vue, such as Lodash https://lodash.com/ https://lodash.com/ A quick example: http://colintoh.com/blog/lodash-10-javascript-utility-functions-stop-rewriting http://colintoh.com/blog/lodash-10-javascript-utility-functi...
kimshibal 10y ago
We have the same result. Our team, junior developers are happier after we made the transition from react to vue. They can do their job in less time than previous frameworks
ozgung 10y ago
"We switched from X to Y and we are never going back." I think I've seen thousands of combinations for X and Y on HN. First everyone switched from JS to JQuery, Then JQuery to Ember or Backbone and never looked back. At one point everyone moved from Ember to Angular and never looked back. Then from Angular to React. Some people even switched from Swift and Java to React Native and never looked back. Then from Flux to Redux. And now I see people switching from React to Vue.js (and even back to JQuery?). And these were just for the Frontend JS libraries. It's all like a cat and mouse game. You cannot win. And I'm not sure there is even real progress. It seems like they are all reinventing the wheel again and again. This also reminds me of Joel's article on "cover fire": http://www.joelonsoftware.com/articles/fog0000000339.html http://www.joelonsoftware.com/articles/fog0000000339.html
- jazoom 10y ago
  Well, since React and Vue 2.0 are so similar it's not a big deal to switch. And yes, I'm not going back to React after experiencing the cohesive and well-thought out Vue. If something super better comes along I might start using that, but I doubt that'll be anytime soon. The improvement needs to be worth The effort to learn the new framework. With React -> Vue the improvement doesn't need to be enormous because it's an easy conversion.
  - rajumuttada 10y ago
    No, I am not going back, in fact I never went back. I switched from Jquery to Angular 1, never went back. I switched from Angular 1 to React, never went back. I switched from React to Angular 2, never went back. I am considering Vue.js, and yes, I will never go back.
    - flukus 10y ago
      That sounds more like a concentration problem than a framework one.
- ef4 10y ago
  The people who are busy productively shipping products are not the ones who spend the most time and attention on these online debates, so it's easy to form a biased impression. It's the developer version of the 24 hour news cycle. The many companies who are steadily and happily shipping valuable products on one stack aren't the ones that generate drama and pageviews. Taking just one of your examples: the Ember ecosystem is large and growing, with many billion dollar businesses standardizing their apps on Ember. But that is too boring compared to "why we switched" posts. "Everyone" turns out to be way bigger than "people you are likely to hear from on HN".
jazoom 10y ago
Can confirm. I've been developing in React for 18 months. Loved 90% of React. Porting to Vue 2.0 now. I think I've found most of that missing 10% of coding joy.
canyonero 10y ago
"React can be fun to learn in the beginning but over time it does cause a lot of fatigue when you need it to do a little more" Could you elaborate on what extra things you'd like react to do for you?

cormacrelf 10y ago

I get the feeling that React with the Redux/Flux architecture scales to Facebook-level complexity a bit better than Vue. Vue feels kinda like if you made plain React with setState a lot easier to use. The complete separation of presentation and state with flux is a lot of work but starts to pay off when your data is used in many places and you can just connect any piece to the same global state and keep consistency. Or when you can make writing API interactions really easy with one middleware and from there your requests are done declaratively with actions. I wonder what it's like to use Vue with Redux! Probably a bit weird given the two-way binding, where Redux is all about one-way binding and cycling every change through a global state transition. At first glance (revue, vue-redux) this seems awkward. How does your team accomplish the stuff you would otherwise do with Redux? How do you do AJAX and how do you propagate that around? I suppose it's just like regular MVVM, all pretty isolated.

wishinghand 10y ago
Just FYI, Vuex is the first party answer for a Redux solution for Vue.
unculture 10y ago
You can totally use Redux, but conceptually Vuex is so similar that you may as well use that. Also, Vue doesn't really have two way binding, just the v-model directive that is syntax sugar for handling an event to update component state.
Etheryte 10y ago
Redux is just a fancy PubSub, you don't need it to scale. The main thing Redux got right was jumping on the React hype train. Don't get me wrong, I write React apps with Redux myself, but Redux is far from being a mandatory component.
jaequery 10y ago
I'm pretty sure 99.999% of websites don't require Facebook complexity. And even if you do require it, I don't see why Vue.js can't handle what Facebook does.

wishinghand 10y ago

Vue-router gets you all of the CRUD operations if that's all you're using jquery for.

patrickdavey 10y ago
Just checking, did you mean vue-router .. or did you mean vue-resource[0]. I've only played with vue a bit so I could be missing something. [0]https://github.com/vuejs/vue-resource https://github.com/vuejs/vue-resource
- wishinghand 10y ago
  I totally meant Vue-resource, but for some reason I keep mixing the two up when I speak or post about them.

BrandoElFollito 10y ago

Would you mind elaborating a bit on "a wide array of utility functions that you would typically use in your vue.js app."? I am an amateur developer (home projects) and started to use Vue which I find excellent. I had the idea, though, that using Vue and jQuery at the same time is not correct (= technically it works but it is not recommended as Vue is supposed to do the jQuery things. If you use jQuery then your Vue design is wrong. Again, this was my understanding). Except for AJAX where I use qwest anyway.

AOsborn 10y ago
You have this pretty much right. You want to avoid overlapping jQuery and Vue for areas both cover such as event binding and DOM manipulation. This should be left to Vue. jQuery provides a number of other functions but AJAX is the major part of this. See https://api.jquery.com/category/utilities/ https://api.jquery.com/category/utilities/ If you already have a solution for AJAX, you might be interested in looking into a more generic library to complement Vue, such as Lodash https://lodash.com/ https://lodash.com/ A quick example: http://colintoh.com/blog/lodash-10-javascript-utility-functions-stop-rewriting http://colintoh.com/blog/lodash-10-javascript-utility-functi...

kimshibal 10y ago

We have the same result. Our team, junior developers are happier after we made the transition from react to vue. They can do their job in less time than previous frameworks

ozgung 10y ago

"We switched from X to Y and we are never going back." I think I've seen thousands of combinations for X and Y on HN. First everyone switched from JS to JQuery, Then JQuery to Ember or Backbone and never looked back. At one point everyone moved from Ember to Angular and never looked back. Then from Angular to React. Some people even switched from Swift and Java to React Native and never looked back. Then from Flux to Redux. And now I see people switching from React to Vue.js (and even back to JQuery?). And these were just for the Frontend JS libraries. It's all like a cat and mouse game. You cannot win. And I'm not sure there is even real progress. It seems like they are all reinventing the wheel again and again. This also reminds me of Joel's article on "cover fire": http://www.joelonsoftware.com/articles/fog0000000339.html http://www.joelonsoftware.com/articles/fog0000000339.html

jazoom 10y ago
Well, since React and Vue 2.0 are so similar it's not a big deal to switch. And yes, I'm not going back to React after experiencing the cohesive and well-thought out Vue. If something super better comes along I might start using that, but I doubt that'll be anytime soon. The improvement needs to be worth The effort to learn the new framework. With React -> Vue the improvement doesn't need to be enormous because it's an easy conversion.
- rajumuttada 10y ago
  No, I am not going back, in fact I never went back. I switched from Jquery to Angular 1, never went back. I switched from Angular 1 to React, never went back. I switched from React to Angular 2, never went back. I am considering Vue.js, and yes, I will never go back.
  - flukus 10y ago
    That sounds more like a concentration problem than a framework one.
ef4 10y ago
The people who are busy productively shipping products are not the ones who spend the most time and attention on these online debates, so it's easy to form a biased impression. It's the developer version of the 24 hour news cycle. The many companies who are steadily and happily shipping valuable products on one stack aren't the ones that generate drama and pageviews. Taking just one of your examples: the Ember ecosystem is large and growing, with many billion dollar businesses standardizing their apps on Ember. But that is too boring compared to "why we switched" posts. "Everyone" turns out to be way bigger than "people you are likely to hear from on HN".

jazoom 10y ago

Can confirm. I've been developing in React for 18 months. Loved 90% of React. Porting to Vue 2.0 now. I think I've found most of that missing 10% of coding joy.

canyonero 10y ago

"React can be fun to learn in the beginning but over time it does cause a lot of fatigue when you need it to do a little more" Could you elaborate on what extra things you'd like react to do for you?