Why we chose Vue.js over React

#1

Post by jetter » Sun, Dec 11, 2016, 3:02 PM UTC

Why we chose Vue.js over React
pixeljets.com

Re: Why we chose Vue.js over React

#2

Post by romanovcode » Sun, Dec 11, 2016, 3:47 PM UTC

In short: FOTM

Re: Why we chose Vue.js over React

#3

Post by tyingq » Sun, Dec 11, 2016, 3:48 PM UTC

I was initially confused about why a Drupal shop would need either Vue.js or React, since Drupal sites are most typically blog like things.

Appears it's for their backend though, and this is actually pretty nice: http://pixeljets.com/sites/default/files/why-we-chose-vuejs-...

Re: Why we chose Vue.js over React

#4

Post by adamnemecek » Sun, Dec 11, 2016, 3:53 PM UTC

It's been a while since I've needed a front end framework but if react doesn't scratch your itch, you should check out cycle.js.

https://cycle.js.org

Re: Why we chose Vue.js over React

#5

Post by andrew_wc_brown » Sun, Dec 11, 2016, 3:58 PM UTC

MITHRIL JS

Re: Why we chose Vue.js over React

#6

Post by conradk » Sun, Dec 11, 2016, 3:59 PM UTC

I've been using Vue.js at work for this kind of thing: http://reassurez-moi.fr/taux-pret-immobilier

It was as simple as adding Vue.js itself and one JS file for custom code. I tried using Angular but right off the bat, I had to install hundreds of dependencies via NPM.

That's what I like about Vue.js. It's simple to reason about for the kind of use case I linked above.

Re: Why we chose Vue.js over React

#7

Post by sergiotapia » Sun, Dec 11, 2016, 3:59 PM UTC

My man, a lot of the pain described in this article can be solved by Mobx: https://stackshare.io/mobx

One of our engineers at StackShare[0] suggested it and it's fantastic.

Mobx is very simple to understand and will make writing a "React" page a real joy again. Redux was way too complicated for what it gave, and just shot term after term after term at me that left me with a headache. I still don't understand Redux proper.

>Why do you have to type so much?

I know! I nope'd away from Redux because of that same reason.

But Mobx clicked for me. And if it clicked for me, it'll click for you.

Basically you have a store and you use that store anywhere in your components to share store state. When you update that store state everywhere else updates as well. Simple.

Another great reason to use React as opposed to alternatives is react-native. A _lot_ of knowledge transfer between the web and mobile with react native. It's pretty insane.

[0] - https://stackshare.io/stackshare/stackshare

Re: Why we chose Vue.js over React

#8

Post by juandazapata » Sun, Dec 11, 2016, 4:00 PM UTC

I'm glad to see that Vue is getting more adepts. Kudos to the core team for making it so easy and accessible for everyone.

Re: Why we chose Vue.js over React

#9

Post by jplusplus » Sun, Dec 11, 2016, 4:04 PM UTC

I believe React is popular (among other reasons) because you don't need to learn what is v-if v-else and other repeative commands when you have plain and simple JS equivalents.

React has te philosophy "It jusy works", and people love this

Re: Why we chose Vue.js over React

#10

Post by k__ » Sun, Dec 11, 2016, 4:05 PM UTC

adamnemecek wrote: post #4

It's been a while since I've needed a front end framework but if react doesn't scratch your itch, you should check out cycle.js. https://cycle.js.org

Really good framework indeed. One of the few who are really good in handling realtime data. Its dataflow-components are much more flexible than React components, which makes it really more flexible.