Live data from Hacker News

The journey from giving up React.js in favor of Vue.js

medium.com

11–20 of 28 posts

Re: The journey from giving up React.js in favor of Vue.js

#11
post #3
post #2

A poorly done React component (mixing props and state?) and what looks to be a poorly done Vue component (with some jQuery lib thrown in?), are the basis of the opinion? Seems weird.

Yeah, pick any framework that you don't know how to use properly, drop it for another framework that you don't know how to use properly, write a post on medium about it, repeat.

Might as well put a link to your e-book in it too, so you can make money when you get on the front page of HN.

Re: The journey from giving up React.js in favor of Vue.js

#13
post #2

A poorly done React component (mixing props and state?) and what looks to be a poorly done Vue component (with some jQuery lib thrown in?), are the basis of the opinion? Seems weird.

Yep, I think a lot of a confusing parts of React components is state and ES6 classes. Luckily, you don't actually have to use those, React really shines (IMO) when you write stateless components, using ordinary functions.

    const MyList = props => (
      
        {props.list.map((item, index) => {item})}
      
    );

    ...

    

Re: The journey from giving up React.js in favor of Vue.js

#14
post #6

Was on the front page for some reason... what is it with the abysmal quality articles advocating vue.js?

I think the differentiating factor is React is much more (dare I say it) enterprise. It shines when you have lots of developers, large codebases, and shared code. Vue is much scrappier and the literature tends to reflect that.

Re: The journey from giving up React.js in favor of Vue.js

#16
post #2

A poorly done React component (mixing props and state?) and what looks to be a poorly done Vue component (with some jQuery lib thrown in?), are the basis of the opinion? Seems weird.

Yep, I think a lot of a confusing parts of React components is state and ES6 classes. Luckily, you don't actually have to use those, React really shines (IMO) when you write stateless components, using ordinary functions. const MyList = props => ( {props.list.map((item, index) => {item} )} ); ...

I have no problem with stateful components, it was with this oddity:

   this.state = {
     value: this.props.value || '',
   }

Re: The journey from giving up React.js in favor of Vue.js

#17
post #4

Seems more like they threw their hands up in frustration and went with something that was more immediately understandable to them. I haven't used Vue yet, but I'm curious how nice it is to develop with after the codebase has grown significantly - I remember Angular 1.x had that same "magic" that made it easy to appreciate and pick up, but ended up being a huge headache after writing production code with it for over a…

React is the only web framework I've ever used that has held up to the trials of a long-lived application. I thought it was pretty good when I first picked it up, two years later and I'm in love with it. That alone makes me incredibly hesitant to try new frameworks.

Re: The journey from giving up React.js in favor of Vue.js

#18

> It’s just a library, so if you want to make use of a fully featured framework, the React guys invented Redux This is wrong; Redux is not a framework, it's just a technique for managing state.

Indeed - very poorly written and very misleading. Redux is just a library for state management which is NOT correlated with React (although people seem to think so because Redux's author now works on React at Facebook).

It wasn't written at all by the "React guys".

It also implies Redux englobes React which it most certainly doesn't - they're just 2 independent libraries.

Re: The journey from giving up React.js in favor of Vue.js

#19
post #5

I find Vue to be such a breath of fresh air. All I wanted out of React was shadow DOM and then it went and turned into this whole cultural movement thing .

> All I wanted out of React was shadow DOM

You can just use that if you'd like.

> turned into this whole cultural movement thing

Isn't that a pretty much foregone conclusion given a large enough adoption and ecosystem? After all, ColdFusion has less of a cultural influence on its users than Rails does.

Post reply on HN