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

51–60 of 177 posts

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

#51

Post by wjossey »

j45 wrote: post #16
wjossey wrote: post #5

I’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 t…

Appreciate the comment about high and low bandwidth performance by vue. 80% of the world is low bandwidth and such solutions built with such tools have an opportunity to have a much farther reach. Have you had any exposure to using vue as a progressive web app that can sync and work offline first? Have you come across any vue.js offline app experiences?

I've looked at PWA & working with offline, but it's an optimization I'd like to have, not one that we absolutely need. Right now, given how crunched we are for resources, everything I work on has to fall into the category of "absolutely need", otherwise I de-prioritize it.

For us, the reason why we don't necessarily "need" PWA or full offline is that we do have an initial online component that is dynamic, so fully supporting an offline mode (a la, full on iOS or Android app) would change a lot of assumptions & optimizations we've made with how our product works. PWA seems promising, but it still feels slightly early to me. It's not that I don't think it will eventually win, but right now it has just enough complexity with minimal payoff, that I've punted for now (although it's probably closest to what we're looking for).

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

#52

Post by wjossey »

platz wrote: post #17
wjossey wrote: post #5

I’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 t…

What is a turbolink?

Yes, sorry for just tossing this one in there. Our product is build on top of rails 5.x, and rails has support for turbolinks. They make your server-side rendered application 'Feel' more SPA, by only refreshing the parts of the page that have actually changed upon server response.

It still requires a massive payload to be sent across the wire, as well as a full render on the server, so it's not the "king of efficiency", but it definitely improves the end user experience in many ways.

In my case, I wanted an even snappier experience, where a user clicking on a button would trigger an immediate transition, with the "saving" happening behind the scenes. Before, on a slow or bogged down connection, you could see page transitions take second(s), which felt like an eternity when you had to go through our 50+ screens during our workshop. Now, with heavier backgrounding, those transitions are instantaneous, and the end-user doesn't need to wait but a millisecond (draw time) for the next page.

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

#53

Post by danabramov »

baybal2 wrote: post #26
acemarke wrote: post #10

Earlier quoted context omitted.

Can you clarify that comment? What aspects of React's development are you concerned with?

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…

What heuristic rules? We don't have any new heuristic rules at the moment. Source: I work on React.

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

#54

Post by faitswulff »

ng12 wrote: post #47
tomonl wrote: post #33

Earlier quoted context omitted.

It works in the part of your .vue file, but not the part.

Ah, that's a bummer. Vue Templates seem wildly regressive to me -- I can't fathom going back to stringly-typed Handlebars wrangling after using JSX/TSX. After looking into this further it seems like Vue Templates also differentiate between values and components. In React I often write components which can take in either: a good example is text which the consumer might want to format. You can easily write the componen…

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

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

#56

Post by CaveTech »

ng12 wrote: post #47
tomonl wrote: post #33

Earlier quoted context omitted.

It works in the part of your .vue file, but not the part.

Ah, that's a bummer. Vue Templates seem wildly regressive to me -- I can't fathom going back to stringly-typed Handlebars wrangling after using JSX/TSX. After looking into this further it seems like Vue Templates also differentiate between values and components. In React I often write components which can take in either: a good example is text which the consumer might want to format. You can easily write the componen…

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.

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

#57

Post by acemarke »

baybal2 wrote: post #26
acemarke wrote: post #10

Earlier quoted context omitted.

Can you clarify that comment? What aspects of React's development are you concerned with?

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…

Your comment is very confusing.

React does not require use of Observables in any way.

I also have no idea what your second and third points could be referring to. If you can supply some links as references, I can try to provide some context or explanation, but at the moment you seem to be making up things that don't exist to complain about.

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

#58

Post by platz »

ec109685 wrote: post #45
platz wrote: post #15

OP predicts with absolute certainty vue "will become dominant" next year many times. Also OP has skin in the game to justify to his team that vue was the correct choice. Nice as an opinion piece but too many red flags to be considered fair and unbiased.

Huh? OP said the power of the React ecosystem and change in license will keep it on top in 2018 and that if they were starting from scratch they probably would have used React for their website.

> next year would be the year of Vue.js success

> Vue.js will be dominating only in the web

OP did not say they would've used React given the choice, they said it would have made some things simpler

Your reading and subtle re-wording of OPs comments misrepresent what OP actually says.

> our stack would be simpler if we chose React.js for the web. We definitely do not regret choosing Vue.js for web, read more in my previous post why we did that, my expectations on Vue.js web domination are becoming the reality

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

#59

Post by jetter »

spion wrote: post #38
jetter wrote: post #18

Earlier quoted context omitted.

I agree. We still admire Vue.js after using it for more than a year and writing hundreds of lines of Vue.js code every day. No chance I would choose React+Redux in cases when I know I need quick progress on my web project - Vue.js allows you to be very productive, cutting corners in the right places, while still keeping the reasonable code quality, and writing very little of boilerplate.

MobX+React would be just like Vue, but with the benefits of the larger React ecosystem and full type checking with typescript/flow, and the drawback of mandatory build tooling.

It is similar, but it will mean you get off the highway of React "preferred way" - for example, in case you start working with React Native you might have an issue of using different state management solutions for your web and mobile stack - it looks like nobody is using Mobx with RN in serious projects.

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

#60

Post by eropple »

jetter wrote: post #59
spion wrote: post #38

Earlier quoted context omitted.

MobX+React would be just like Vue, but with the benefits of the larger React ecosystem and full type checking with typescript/flow, and the drawback of mandatory build tooling.

It is similar, but it will mean you get off the highway of React "preferred way" - for example, in case you start working with React Native you might have an issue of using different state management solutions for your web and mobile stack - it looks like nobody is using Mobx with RN in serious projects.

I've used MobX for React Native (though I went back to Redux for familiarity). I found it to be transparent enough.
Post reply on HN