Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vue.js vs. React: what happened in 2017

pixeljets.com

Post reply on HN
Print view View original

91–100 of 177 posts

Re: Vue.js vs. React: what happened in 2017

#91

Post by badbanana »

Having used both React (with Typescript and Redux) and the latest Vue (with es6 and Vuex) I prefer React, and I don't even use React Native.

Vue is better for onboarding people more in tune with "classic" html + js development; and that's where the advantages end as far as I'm concerned. This might be a big win for some people.

The way I reason about it is that React is simple, Vue is easy. When you take into account Vue's templating language, React's api is small in comparison. A beginner won't know how to do some common use cases reading React's docs, when Vue might have a something built-in in its templating language (e.g. slots, or the component tag for dynamic components).

Slightly annoyed with Vuex too because of its slightly leaky abstraction. You have to remember to setup the properties you mutate so the reactivity will detect a change; and also remember not use array indexes arrays cause it can't detect changes otherwise. The array index thing will be fixed in the next version when they drop support for some older IE. Using Typescript would probably help a bit here, although Typescript being useless for checking Vue templates really feels like a huge chunk of its value is wasted.

Typescript is not currently available in the official blessed boilerplate which greatly affects its uptake in the Vue community.

Anyway, if you already know React, there is zero advantage in investing time in Vue.

Re: Vue.js vs. React: what happened in 2017

#92

Post by perlgeek »

Isn't it funny how you can read different things into the same data?

> So, 1 year passed, and Vue.js is clearly the leader in "would like to learn" by a huge margin

For me, the main takeaway of the newer chart is "React is the clear winner in the 'Happy Customer' category".

For the record, I never used any of the frameworks, though I think I will, some day.

Re: Vue.js vs. React: what happened in 2017

#93

Post by shard972 »

badbanana wrote: post #91

Having used both React (with Typescript and Redux) and the latest Vue (with es6 and Vuex) I prefer React, and I don't even use React Native. Vue is better for onboarding people more in tune with "classic" html + js development; and that's where the advantages end as far as I'm concerned. This might be a big win for some people. The way I reason about it is that React is simple, Vue is easy. When you take into account…

I have already moved to using React for my larger projects and Mithril for my smaller ones instead of Vue because of the lack of typescript support.

That and when you add JSX to mithril, the api just feels so simple and i rarely find myself checking the docs for something.

Re: Vue.js vs. React: what happened in 2017

#95

Post by rsyring »

shard972 wrote: post #93
badbanana wrote: post #91

Having used both React (with Typescript and Redux) and the latest Vue (with es6 and Vuex) I prefer React, and I don't even use React Native. Vue is better for onboarding people more in tune with "classic" html + js development; and that's where the advantages end as far as I'm concerned. This might be a big win for some people. The way I reason about it is that React is simple, Vue is easy. When you take into account…

I have already moved to using React for my larger projects and Mithril for my smaller ones instead of Vue because of the lack of typescript support. That and when you add JSX to mithril, the api just feels so simple and i rarely find myself checking the docs for something.

Glad to see Mithril mentioned. I like it better than React when comparing the APIs, It just seems simpler. But React obviously has the mind share. I'd love to see Mithril gain momentum.

I especially like the fact that I can easily include it as a script, like Vue, and don't have to have a build chain. That really decreases complexity for smaller projects.

Re: Vue.js vs. React: what happened in 2017

#96

Post by baybal2 »

acemarke wrote: post #83
baybal2 wrote: post #77

Earlier quoted context omitted.

There is no explicit dependency on RXJS or its analogs, but the whole ecosystem is heavily tied to on them. A question "how to do thing A when user changes thing B" on React forums is usually dismissed with "just use MobX/Rxjs/Kefir/Bacon"

Citation Needed, please. The most basic approach for responding to a change in data is to compare the previous and current props in the `componentWillReceiveProps` or `componentDidUpdate` lifecycle methods. Meanwhile, Redux is the most common state management library used with React apps. You certainly _can_ use MobX, RxJS, or some other FRP-type library with React, but to claim that "the whole ecosystem is heavily t…

>but to claim that "the whole ecosystem is heavily tied to them" is simply wrong, and shows a gross misunderstanding of the React world.

May be, but this is how it looks from my part of the world, which is Russia or China when I am doing term contracts there from time to time.

Here, the so called "software evangelists", apparently paid or hired by FB, swarm tech events to lecture people on how to do "10 tricks to transform your eCommerce business with Agile management, and FLUX pattern". And they get pretty annoying. My experience with React ends with my interaction with them and doing basic demos for recruitment interviews. I have not yet heard of a FRP-framework-free React site being considered norm for a "serious project" here.

Just like those FB "evangelists" do today, Angular proponents were doing the same 5 years ago with their maxim: "the magic provider/factory/service pattern is the new best thing since a sliced bread" without elaborating much why. That lead to many mentally-infirm developers trying to shove it everywhere, making usage of Angular ecosystem without zealous following of that pattern impossible.

I have impression that the same is happening with FRP-everywhere crowd and React.

If this isn't how it is, I am glad.

Re: Vue.js vs. React: what happened in 2017

#97

Post by acemarke »

rsyring wrote: post #95
shard972 wrote: post #93

Earlier quoted context omitted.

I have already moved to using React for my larger projects and Mithril for my smaller ones instead of Vue because of the lack of typescript support. That and when you add JSX to mithril, the api just feels so simple and i rarely find myself checking the docs for something.

Glad to see Mithril mentioned. I like it better than React when comparing the APIs, It just seems simpler. But React obviously has the mind share. I'd love to see Mithril gain momentum. I especially like the fact that I can easily include it as a script, like Vue, and don't have to have a build chain. That really decreases complexity for smaller projects.

FWIW, you can absolutely use React as just a pair of script tags - see the "React Single-File Example" template [0].

It's certainly common to use React in a larger application that uses a build chain, and that's the recommended approach, but it's not required.

[0] https://raw.githubusercontent.com/reactjs/reactjs.org/master...

Re: Vue.js vs. React: what happened in 2017

#98

Post by jonreem »

nawitus wrote: post #87
lsdafjklsd wrote: post #76

I really don't get the love around vue... I always read the glowing sentiment and go, "Ok, I'm missing something, let me go back to the vue.js docs and see what's good" Things that are a deal breaker for me: Template language... You can call it 'separation of concerns' all you want, but just let me generate templates using the language I already know, JSX is great State management... I cut my teeth with Ember profess…

"Template language... You can call it 'separation of concerns' all you want, but just let me generate templates using the language I already know, JSX is great" Not everyone knows JSX, so while that argument applies to you, it doesn't apply in general.

They mean javascript; jsx is a very small amount of new syntax and is embedded in normal javascript. Learning a completely separate template language with all of its own constructs for conditionals, iteration, etc. is significantly more work.

Re: Vue.js vs. React: what happened in 2017

#99

Post by acemarke »

baybal2 wrote: post #96
acemarke wrote: post #83

Earlier quoted context omitted.

Citation Needed, please. The most basic approach for responding to a change in data is to compare the previous and current props in the `componentWillReceiveProps` or `componentDidUpdate` lifecycle methods. Meanwhile, Redux is the most common state management library used with React apps. You certainly _can_ use MobX, RxJS, or some other FRP-type library with React, but to claim that "the whole ecosystem is heavily t…

>but to claim that "the whole ecosystem is heavily tied to them" is simply wrong, and shows a gross misunderstanding of the React world. May be, but this is how it looks from my part of the world, which is Russia or China when I am doing term contracts there from time to time. Here, the so called "software evangelists", apparently paid or hired by FB, swarm tech events to lecture people on how to do "10 tricks to tra…

I certainly don't claim to know everything that goes on in the React ecosystem (especially outside the US), but I _am_ pretty tuned in with the major trends and discussions that are going on, and I've seen plenty of real-world React applications and codebases. None of that matches anything I've seen thus far.

I have never heard of Facebook paying "software evangelists". I suppose it's possible, but it really doesn't match with what I know about how Facebook develops and uses React.

Re: Vue.js vs. React: what happened in 2017

#100

Post by ausjke »

vuejs does gain strong interests from large companies such as alibaba,baidu and tencent, the three are called BATs in China similar(or larger) to amazon, google and facebook in US.

One of the BAT should acquire Vue.js to make it a strong player for the long run, that may happen in 2018 I hope.

Both laravel and vue.js (vue.js is the default frontend choice and embedded in Laravel) are from one core developer, I liked them, but am concerned about the bus factor. I eventually choose nodejs+react because of that.

Post reply on HN