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

81–90 of 177 posts

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

#81

Post by moomin »

dustingetz wrote: post #22

I write ClojureScript A good indicator of if a technology is going to explode, is if emerging language users are excited about it, as good ideas tend to trickle down from the more advanced/research-y ecosystems which aren't as constrained by legacy. So for example React was built by a user of OCaml. ClojureScript early adopted React.js through the Om project in 2013 and there is a growing number of competing React ad…

Speaking as someone who writes ClojureScript themselves, ClojureScript is definitely in the category of technologies that show no sign of explosion whatsoever.

React and Vue are both great technologies, but with Teact the template syntax is optional, and no lisp user wants another syntax...

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

#82

Post by Mary-Jane »

ng12 wrote: post #70
faitswulff wrote: post #54

Earlier quoted context omitted.

You don't have to use the templates, though. Define a render function and you can even use JSX in it: https://vuejs.org/v2/guide/render-function.html#JSX

Why wouldn't I just use React at that point? Same behavior, less complexity.

I agree; using JSX outside React feels kinda silly. But Vue is much simpler to grok than React.

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

#83

Post by acemarke »

baybal2 wrote: post #77
baybal2 wrote: post #26

Earlier quoted context omitted.

First, probably was their approach to implicitly require use of Observable objects everywhere. Second, use of arcane CS lingo and authors writing 10 pages long pages on every known MVC model, FLUX, SCHMUX and etc with weekly regularity. Third, during transition to Fiber, they went on gigantic increase of complexity by introducing a lot of what can be said to be heuristic rules, and all for non-guaranteed, minor perfo…

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 tied to them" is simply wrong, and shows a gross misunderstanding of the React world.

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

#84

Post by mamcx »

fictionfuture wrote: post #2

I see a lot of commits from the Vue team into the core repo that are meant to support use in native. Likely, we can expect something comprehensive for native this year. I also believe it's a smart strategy to avoid Facebook codebases because they are all meant to somehow benefit FB in some (usually dubious) way. Also the Vue approach is 1000% cleaner in practice than React, just doesn't have the bandwagon effect goin…

A thing that will sell vue/react native for me is the ability to only use them for UI. I don't wanna use them for logic or heavy stuff. Just have them for render the UI.

This mean, easy way to embedb into iOS/Xamarin.NET.

I have look at react native and NativeScript and both are very hack-ish for my taste.

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

#85

Post by bwilliams »

baybal2 wrote: post #77
baybal2 wrote: post #26

Earlier quoted context omitted.

First, probably was their approach to implicitly require use of Observable objects everywhere. Second, use of arcane CS lingo and authors writing 10 pages long pages on every known MVC model, FLUX, SCHMUX and etc with weekly regularity. Third, during transition to Fiber, they went on gigantic increase of complexity by introducing a lot of what can be said to be heuristic rules, and all for non-guaranteed, minor perfo…

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"

> There is no explicit dependency on RXJS or its analogs, but the whole ecosystem is heavily tied to on them.

That's flat out untrue. This might be some people's approach but in all my years of writing React apps as a consultant I haven't had to use any of those libraries on a project.

FWIW that problem is usually solved by reorganizing code a bit and passing a callback down.

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

#86

Post by ricardobeat »

dustingetz wrote: post #67
murukesh_s wrote: post #48

Earlier quoted context omitted.

Not necessarily.. I wonder had react not been backed by FB, it certainly would have had a beating in its popularity given lighter and arguably faster alternatives like vue. Remember, performance was one of the main argument React had when compare to Angular. Now since performance is no more a differentiating factor, developers might look into other aspects like better ROI in short and long term..

vue wouldn't even exist if react had not paved the way first

Not true - Ractive is a library much like vue on the surface that came out _before_ React. It's all about timing, promotion and hitting a feature sweet spot.

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

#87

Post by nawitus »

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.

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

#88

Post by ricardobeat »

ng12 wrote: post #71
CaveTech wrote: post #56

Earlier quoted context omitted.

You can use slots to pass HTML or Components into child components. You can have vue render jsx or templates, but in practice you can make interactive components very simply using templates which are foundationally simpler and easier to grasp than JSX.

How so? In my mind templates and JSX are equally complex from a user standpoint. In fact I'd argue that JSX is simpler because you don't have to invent slots -- it's an obvious side effect of using JavaScript to generate your structure. Just reading about slot and slot-scope makes me think Vue's reputation for simplicity is overblown.

It may seem "obvious" to you after being in the water with JSX for a while, but the free-style abstractions afforded by being 'just' JavaScript, like the one you mention, look incredibly complex for someone approaching an unknown codebase.

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

#89

Post by jjeaff »

sarahcross wrote: post #6

React changing their license probably saved them. My web dev office was going to transition from them until they changed it.

Same here. For us personally, the license made no difference. We know we will never come across any patent issues with Facebook. But the fact that it existed led us to believe that in the long run an alternative would emerge since larger corps would avoid it because of the license.

Now that they got rid of it, I have no such concern investing time in react for the short/mid term term.

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

#90

Post by jjeaff »

buamaharami wrote: post #36

Why in earth people would like to to use anything from facebook in they business ? Why do you trust they licensing ? I would choose riotjs or vuejs anyday before any facebook's code in my apps.

Facebook has corrected the licensing issue. Most consider it a non-issue now. And I think Facebook proved with that move that they are willing to play ball.
Post reply on HN