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

Why we chose Vue.js over React

pixeljets.com

Post reply on HN
Print view View original

31–40 of 267 posts

Re: Why we chose Vue.js over React

#31

Post by inglor »

ceejayoz wrote: post #23
inglor wrote: post #13

Earlier quoted context omitted.

VueJS is pretty old, old enough to be there when React and Angular were just emerging as viable options. It's great, and I'm grateful for it being around and for Evan's contribution but I think it was pretty lucky timing wise.

Angular was released in 2010. Vue was released in 2014. Bit weird to call it "pretty old", and Angular was well established by then - they announced the v2 preview around the same time.

2014 was the year Angular "really took off" and 2015 was the year React "really took off" (at least, if we trust "Google Trends")

Vue is, in its core, very similar to Knockout (which I think is pretty swell). I think coupled with a better DOM abstraction (like React) it can do great thing - that's what MobX does and why I like it.

I sympathize with the post's sentiment of giving UI people work.

Re: Why we chose Vue.js over React

#32

Post by welanes »

inglor wrote: post #13
welanes wrote: post #11

One of the most impressive thing about Vue.js was the ability of the framework to enter a field saturated with dozens of options, that was becoming dominated by a well-resourced oligopoly (Angular, React), and still win over developers jaded from Javascript-fatigue. The give-a-shit factor from Evan (the creator) is extremely high and was key to its success. Inspiration for anyone building a product in an established…

VueJS is pretty old, old enough to be there when React and Angular were just emerging as viable options. It's great, and I'm grateful for it being around and for Evan's contribution but I think it was pretty lucky timing wise.

A good place to start a comparison is when using Vue.js in production looked viable - the October 2015 V1.0 release. At that point Angular has amassed 46k github stars, React had 35k.

Star counts don't tell us everything but they're an OK heuristic of how many people are invested in a library at a point in time. Had Vue.js been in anyway meh it wouldn't have made such a dent in people's attention.

Timing luck, insofar as it exists, is probably weighted towards arriving later. Vue had a chance to listen to the market and solve some of the headaches that developers were voicing about incumbents. V2.0 is basically the best bits of Angular and React.

Again, lots of lessons for product creators.

Re: Why we chose Vue.js over React

#33

Post by adamnemecek »

k__ wrote: post #10
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.

Also everything I've read from the author http://staltz.com/ I either agreed with (http://staltz.com/all-js-libraries-should-be-authored-in-typ...) or found really illuminating (http://staltz.com/unidirectional-user-interface-architecture...).

Re: Why we chose Vue.js over React

#34

Post by devoply »

welanes wrote: post #11

One of the most impressive thing about Vue.js was the ability of the framework to enter a field saturated with dozens of options, that was becoming dominated by a well-resourced oligopoly (Angular, React), and still win over developers jaded from Javascript-fatigue. The give-a-shit factor from Evan (the creator) is extremely high and was key to its success. Inspiration for anyone building a product in an established…

The reason for its success is good documentation and simplicity. Anything like this aims to empower users, and get the fuck out of the way and let them do their work has a space no matter how crowded the market.

Angular and React want you to do things their way and therefore get in the way, and then make you do a bunch of work to make things work their way. I have a PHP app that I rigged up using Vue.js. Took two days to do. Had to change nothing in the app, instead of rendering views with PHP they are output using JSON simple enough. Powerful. Can't do that with Angular for sure. Don't have time to deal with react and its nuances.

Re: Why we chose Vue.js over React

#35

Post by joatmon-snoo »

Out of curiosity, one reason the author mentions (and I know, it's not his selling point) which I've seen others reiterate is that React's render() method doesn't support if statements. I know you can write something like the code below in React, so what exactly does that criticism refer to?

    function Home(props) {
      return (
        
          HELLO
          
Duis a turpis sed lacus dapibus elementum sed eu lectus.

          { (() => {
            if (props.location.query.home) {
              return ( 
You specified a home query: { props.location.query.home }
 );
            }
            else {
              return ( 
No home query was specified.
 );
            }
          })()}
        
      );
    }

Re: Why we chose Vue.js over React

#36

Post by eternalban »

ronocod wrote: post #17

I'm not sold on the whole "code quality" vs "getting things done" mentality here. I think there are diminishing returns in reducing technical debt and keeping a high quality codebase, but the point of doing it that you can maintain a sustained, relatively high "getting things done" rate over the project's lifetime. There are times where you should implement something in a quick and easy way, but if code is going to b…

> I'm not sold on the whole "code quality" vs "getting things done" mentality here.

https://vuejs.org/v2/guide/comparison.html

Based on above, I don't think the dichotomy you pose is applicable in this comparative case.

Re: Why we chose Vue.js over React

#37

Post by _xhok »

I find it completely unbearable to use React with plain JS. I have to use at least Coffeescript and if possible Livescript or Clojurescript. Vanilla JS is just too clunky.

The problem with JS is there are too many patterns in the code, like the mentioned list.map(function(whatever) { ... }). Because JS is a medium power language it doesn't let you abstract this stuff with macros or at least rewrite the syntax.

Coffee and Live provide some relief, but Clojurescript is heaven.

Re: Why we chose Vue.js over React

#38

Post by [deleted] »

tyingq wrote: post #3

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-...

[deleted]

Re: Why we chose Vue.js over React

#40

Post by inglor »

welanes wrote: post #32
inglor wrote: post #13

Earlier quoted context omitted.

VueJS is pretty old, old enough to be there when React and Angular were just emerging as viable options. It's great, and I'm grateful for it being around and for Evan's contribution but I think it was pretty lucky timing wise.

A good place to start a comparison is when using Vue.js in production looked viable - the October 2015 V1.0 release. At that point Angular has amassed 46k github stars, React had 35k. Star counts don't tell us everything but they're an OK heuristic of how many people are invested in a library at a point in time. Had Vue.js been in anyway meh it wouldn't have made such a dent in people's attention. Timing luck, insofa…

At that time React wasn't V1 either. Vue was used and adopted well before 1.0, I had apps for it in the v0.10 days.
Post reply on HN