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

61–70 of 177 posts

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

#61

Post by bpicolo »

dustingetz wrote: post #22

I write ClojureScript A good indicator of if a technology is going to explode, is if emerging language users are excited about it, as good ideas tend to trickle down from the more advanced/research-y ecosystems which aren't as constrained by legacy. So for example React was built by a user of OCaml. ClojureScript early adopted React.js through the Om project in 2013 and there is a growing number of competing React ad…

Ehhh, I don't think that's really telling in this case. Clojurescript layers plenty on top React, so it's really just a library layer over which cljs devs write entirely different DSLs.

The Vue reactive and dom model is pretty much entirely the same as React, it's just its layout for frontend applications that's wildly different. Even if you wanted the component-file style thing in clojure (or html-templates), you wouldn't need Vue to do it.

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

#62

Post by Silhouette »

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…

It looks like you might be conflating React with some other parts of the ecosystem that has built up around it. React retains a far simpler API than the heavier JS frameworks, and AFAIK it doesn't need or do any of the things you mentioned there on its own.

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

#63

Post by m_ke »

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.

We're using RN with mobx and it has been great. We'd probably have 3x more code if we went with redux.

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

#64

Post by Silhouette »

murukesh_s wrote: post #48
rvanmil wrote: post #41

Earlier quoted context omitted.

Agreed, it’ll take another paradigm shift to switch to something else.

Not necessarily.. I wonder had react not been backed by FB, it certainly would have had a beating in its popularity given lighter and arguably faster alternatives like vue. Remember, performance was one of the main argument React had when compare to Angular. Now since performance is no more a differentiating factor, developers might look into other aspects like better ROI in short and long term..

Just as one anecdotal data point, we didn't choose React for its performance when evaluating tools for our recent projects. (React can still be orders of magnitude slower than localised direct DOM updates on demand, after all, and in cases where performance really matters that might still be what you have to fall back on.)

The game-changer with React is that it presents a declarative way to specify your DOM content, which in turn can significantly reduce the number of cases you have to consider in your rendering and state management code, and it's fast enough to make that work in a lot of real world situations.

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

#65

Post by bpicolo »

undershirt wrote: post #14
baybal2 wrote: post #9

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

Hmm, Vue is the one that reminds me of Angular, since it seems to emphasize the ease of constructing views, by its two-way data binding and custom directive syntax inside html. I enjoyed the "Why Vue.js" video. It communicated to me that Vue is really trying to design an easy path (even for non-programmers) to use React's patterns, by mixing in some old ideas that people are familiar and comfortable with.

Vue data is one-way binding these days. There’s a separate way to do two way binding for forms though (which is really a much more convenient mechanism for forms)

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

#66

Post by throwaway0255 »

One thing I'm noticing about SPAs is that they're often slower to load, but the slowness and loading animations gives me a higher perception of the quality of the application.

The same application loading and doing things instantly as server-side templates feels comparatively cheap and un-modern.

What is wrong with me?

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

#67

Post by dustingetz »

murukesh_s wrote: post #48
rvanmil wrote: post #41

Earlier quoted context omitted.

Agreed, it’ll take another paradigm shift to switch to something else.

Not necessarily.. I wonder had react not been backed by FB, it certainly would have had a beating in its popularity given lighter and arguably faster alternatives like vue. Remember, performance was one of the main argument React had when compare to Angular. Now since performance is no more a differentiating factor, developers might look into other aspects like better ROI in short and long term..

vue wouldn't even exist if react had not paved the way first

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

#70

Post by ng12 »

faitswulff wrote: post #54
ng12 wrote: post #47

Earlier quoted context omitted.

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

Why wouldn't I just use React at that point? Same behavior, less complexity.
Post reply on HN