Live data from Hacker News

Vue.js vs. React: what happened in 2017

pixeljets.com

31–40 of 177 posts

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

#31
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.

Agree, also drawing conclusions form "heard of it would like to learn" on the graph seems a bit far fetching. I would like to learn vue but I do not see opportunities in my job to use it next year.

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

#32
When it comes to UI need to start thinking past Framework A vs Framework B. There is already a browser-native compatibility layer known as the Web Components API that allow components rendered by different frameworks to work together, so we won't ever have to be stuck in Framework A or Framework B and can migrate in agile manner (one component at a time) from one to the other or whatever new framework may come next year. I agree Web Components have some major warts and DX issues but libraries like SkateJS and others help smooth those out. Copying from Readme my WIP project that uses Skate: "SkateJS allows us to export components rendered by React, Angular 2, 4, Vue, and other modern composition-oriented frameworks as W3C Custom Elements and compose those Custom Elements into higher order Custom Elements with data flowing from parent to descendants and so on. With SkateJS we can have an Angular 4-rendered Form custom element composing Angular 2-rendered input and selection custom elements, or the other way around with Angular 2-rendered Form custom element composing Angular 5 --and Angular 4-- rendered input and selection custom elements. SkateJS also provides a Router that is framework agnostic. Only the rendering part of any framework (Angular, React, Preact, Vue, et al) is ever used. This way we can build SkateJS-based reusable component libraries using any version of Angular (> 2), React, Vue et al and be able to use those components in our SkateJs-based site together, including via composition, and be able to upgrade our app (when a new version of React, Angular or Vue et al comes out) one component at a time, in piecemeal fashion as in iterative agile development, as opposed to having to do it all at once, as in waterfall development, which is almost always an unrealistic approach. This works because our components are essentially all custom elements regardless of rendering library we use (different versions of Angular, React, Preact, Vue, et al)"

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

#33
post #8

Do 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.

Since October (I think) vue single file components work flawlessly with typescript. Can't speak for jsx though.

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

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

#34
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.

Regardless of React's minor growth in complexity it still pales in comparison to Angular's api from a new learners perspective. After finishing a project in Angular I still feel dumb to it's central concepts. React made sense before I wrote anything.

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

#35
post #26

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…

[deleted]

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

#37

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…

This is my reasoning too. Until someone creates a better reagent and reframe and renatal I'm gonna stick with React

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

#38
post #18
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…

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.

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

#40
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.

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

He is probably Front-End developer with zero knowledge of actual programming. That's why he hates Angular+Typescript.
Post reply on HN