Vue.js vs. React: what happened in 2017
pixeljets.com
Vue.js vs. React: what happened in 2017
1–10 of 177 posts
Re: Vue.js vs. React: what happened in 2017
#2I 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 going for it
Re: Vue.js vs. React: what happened in 2017
#3Good assessment. To summarize the argument, Vue.js is just as good and some would argue better than React for web development, but the React ecosystem really puts it over the top, especially React Native.
Re: Vue.js vs. React: what happened in 2017
#4I truly love Vue and hope it evolves and spreads everywhere.
Re: Vue.js vs. React: what happened in 2017
#5I’m the founder writing code (but not the only technical person) for my three person startup. In October I started migrating our MVP from server side templates to Vue, given we had direction and traction on a product line that justified the time investment. It’s turned out to be a great decision (although likely one that could have been made with react as the choice as well).
My “success story” is how Vue helped me to massively improve our user experience in low bandwidth or high latency environments. Our startup is trying to reinvent the ways that companies approach their review process, and one of the things we do is run a workshop on delivering actionable feedback during the review cycle. We have users log into our app during the workshop, and this often happens in conference rooms over congested WiFi. Our MVP used turbolinks, so it felt generally “snappy” during normal use, but could feel sluggish if moderate latency was introduced (such as a congested router).
Since I completed the rewrite to Vue (which took only about two weeks because of how simple it was to pick up, even for a non frontend person like myself), we’ve had multiple launches that both would have likely bombed had we not done the work to move to something less dependent on a tradition client -> server -> client response cycle to render the next “page”.
Either way, I’ve become an advocate for vue. I love single file components, love the documentation, and am very happy with the community libraries. All in all, I’m very bullish for Vue in 2018 as a happy new users.
Re: Vue.js vs. React: what happened in 2017
#6React changing their license probably saved them.
My web dev office was going to transition from them until they changed it.
Re: Vue.js vs. React: what happened in 2017
#7I 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…
My typical use case doesn't need native apps - a PWA is good enough for me. I will not comment on speculation about the compile-to-native feature because personally it is irrelevant.
I can say that as you I prefer Vue over React and some of my personal reasons are:
* I like opinionated frameworks
* I don't like to mix Javascript and HTML - I can handle a Vue template to any designer but I would not trust a JSX file to a non-programmer.
* Vue is easier for developer onboarding - with Vue the gap between a junior and a senior developer is way smaller.
React may be better, I don't care, Vue is easier for my development style.
Re: Vue.js vs. React: what happened in 2017
#8Do Vue templates play nicely with Typescript? That's something I love about JSX -- "it's just JavaScript" is an incredibly sublime feature. I know you can use JSX with Vue but I'm skeptical since it's a first-order feature with React.
Re: Vue.js vs. React: what happened in 2017
#9I'm afraid React is eventually turning into Angular. At some point, I felt that Angular is somebody's PhD work exploring arcane computer science concepts, not a piece of software for practical use.
React gets closer to that with each year.
Re: Vue.js vs. React: what happened in 2017
#10I'm afraid React is eventually turning into Angular. At some point, I felt that Angular is somebody's PhD work exploring arcane computer science concepts, not a piece of software for practical use. React gets closer to that with each year.
Can you clarify that comment? What aspects of React's development are you concerned with?