Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Why I left React for Vue (sourcerer.io)
3 points by octosphere on Nov 24, 2018 | hide | past | favorite | 3 comments


I've only ever heard positives from react-> vue movers.

I want to hear negatives and positives from vue -> react movers, however small they may be


My first honest question is why?

My personal experience is that I chose Vue over React for use on projects. I also work on projects that have chosen React. Having used both I prefer Vue as the code base tends to stay cleaner with better separation between logic and presentation. Also components tend to be less tightly coupled than on React projects using a Redux store (so I can't comment on how MobX usage might change that).

I can see how the use of PropType validations in React can be a benefit for larger projects being developed by larger teams.

> you won’t have to use setState or any equivalent with Vue

Vue also has some idiosyncrasies and sometimes have to use this.$set() or Vue.set().


Vue doesn't have quite the same dev experience w/ TypeScript as React.

If I were just using ES6, I think it would be a toss-up or Vue would win. With TypeScript, React + TSX wins by a lot. That said, things may have improved with Vue + TypeScript, haven't looked into it in a while.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: