Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Switching From React To Vue.js

vuejsdevelopers.com

Post reply on HN
Print view View original

131–140 of 186 posts

Re: Switching From React To Vue.js

#131

Post by [deleted] »

buchanaf wrote: post #94
wereHamster wrote: post #38

Earlier quoted context omitted.

react-router, do you mean v1, v2, v3, or v4 (or perhaps v5 and v6, I haven't checked if there was a new release with breaking API changes during the past 12 hours).

I mean react-router is almost a 3 year old library trying to handle a rather complex problem. The first three versions were largely the same with no major changes that I can think of except for switching from context to higher order functions. I think everyone is a little dramatic about the number of versions of the library, especially when they are going to continue to support v3.

[deleted]

Re: Switching From React To Vue.js

#132

Post by chrislgrigg »

I think it's important for any comment or post touting the superiority of Vue to also provide insight into the author's experience with and feeings about React. You very rarely hear from devs who were loving React, tried Vue anyway, and came away believers. This leads me to wonder whether it's not so much that Vue is "better," it's more that it operates in paradigms that are intuitive to some individuals and teams in ways that React might not be. I don't see that as a hit against it or anyone but as a very satisfied React, it does make me take every glowing Vue writeup with a grain of salt.

Re: Switching From React To Vue.js

#133

Post by city41 »

yunyu wrote: post #4
yunyu wrote: post #2

The major problem with this tutorial is that it doesn't cover single file components ( https://vuejs.org/v2/guide/single-file-components.html ) at all, which are superior to (and preferred to) implementing string based render functions (which rely on a runtime template compiler). Indeed, the Vue NPM package doesn't even provide the runtime template compiler by default. Stuff like what the article promotes are great f…

Turns out it's mentioned lower down, but the focus of the article is still on Vue.component, which really shouldn't be the case.

I've never used Vue, and in many ways am the target audience of this post. From my perspective, I think he took the right approach. Starting right off with a .vue file would be pretty alien to newcomers.

Re: Switching From React To Vue.js

#134

Post by tyrw »

chrislgrigg wrote: post #132

I think it's important for any comment or post touting the superiority of Vue to also provide insight into the author's experience with and feeings about React. You very rarely hear from devs who were loving React, tried Vue anyway, and came away believers. This leads me to wonder whether it's not so much that Vue is "better," it's more that it operates in paradigms that are intuitive to some individuals and teams in…

They are pretty similar, though one thing this article lightly touches on is the standalone .vue file, which works absolutely beautifully. JSX feels like a hack to me, and the ability to write HTML, JS, and CSS as such in a single file greatly simplifies everything. You can even use different flavors of each (ES6, Sass, etc) no problem. I would be shocked if this feature doesn't find it's way into react, angular, and others.

Re: Switching From React To Vue.js

#135

Post by tyrw »

jorgec wrote: post #44

I don't get it. Lets say that you have a well formed team, then you have a designer. A designer is who does the UI but know or care so little about programming. With React, the UI is practically JSX that very few people know (in comparison with html) and what we will get instead?, the result is the same html that it tries to avoid.

"Lets say that you have a well formed team"

Aaaand you've just just 90% of projects...

Re: Switching From React To Vue.js

#136

Post by intellectable »

twii wrote: post #42

Working with React for almost 3 years now. Came from Angular, Bootstrap, jQuery, etc.. Done small and very large projects with it. It scales better than anything I've used before. It's amazingly reliable and robust. Looking at Vue I cannot think of 1 single benefit I gain by switching. It doesn't even come close to what React is capable of imao. I really have no clue why people are pushing this at all.. Are there any…

Vue has electrolytes and it is gluten free. Seriously though I think Vue is the latest shiny example of everything that is wrong with the javascript community.

Javascripts huge problem is the lack of a standard library or better yet a standard way of doing anything. To fill that void alone came NPM. With a million tiny fragmented micro libraries. Then it became a common to start reinventing the wheel and selling your idea to build up your community by claiming the trivial syntax changes make it so much easier to use. I like you have no clue why people are getting so excited about rewriting their apps all the time.

I think of Vue like attempting to reinvent the calculus of react with a clever syntax and more simplified form but results in a Riemann approximation.

I think Vue is more frontend focused where react is achieving far more like react fiber. I do not doubt the power of js community to keep cloning things into forms they are more familiar with and claim a smaller payload is best metric of success.

Who would have thought so much open source collaboration would lead to so much fragmentation?

I wonder what machine learning algos will come up with when they design their own programming language, because I think programming languages are being held back by discussing what syntax makes me feel good to type out.

Re: Switching From React To Vue.js

#137

Post by bertjk »

Blixs wrote: post #9

I have (some) experience with both React and Vue 2 and definitely prefer the later. Vue is very minimalistic but unlike React provides a lot of functionality out of the box. Stuff like the router, the computed properties, automatic change detection, HTML templates, scoped css, animations, ... . But what's more important is the fact it does all these things in an extremely elegant and unobtrusive way. The computed pro…

Coming from a small-team Rails background, I tried React for a few months, then tried Vue. I found with React I felt compelled to replace and relearn large parts of my stack, and the learning curve as a result was very steep. In comparison adding Vue components to an existing Rails app was dead simple, and I even got to keep writing my Vue templates in HAML. All the questions I had were easily answered by the Vue documentation without even going to e.g. stackoverflow. Vue was the clear winner for me here.

Re: Switching From React To Vue.js

#138

Post by bertjk »

Blixs wrote: post #9

I have (some) experience with both React and Vue 2 and definitely prefer the later. Vue is very minimalistic but unlike React provides a lot of functionality out of the box. Stuff like the router, the computed properties, automatic change detection, HTML templates, scoped css, animations, ... . But what's more important is the fact it does all these things in an extremely elegant and unobtrusive way. The computed pro…

Coming from a small-team Rails background, I tried React for a few months, then tried Vue. I found with React I felt compelled to replace and relearn large parts of my stack, and the learning curve as a result was very steep. In comparison adding Vue components to an existing Rails app was dead simple, and I even got to keep writing my Vue templates in HAML. All the questions I had were easily answered by the Vue documentation without even going to e.g. stackoverflow. Vue was the clear winner for me here.

Re: Switching From React To Vue.js

#139

Post by pluma »

wereHamster wrote: post #38
danmaz74 wrote: post #29

Earlier quoted context omitted.

Redux has been from the same github org for a very long time too: https://github.com/reactjs/redux And react-router, while not being on the same github, is pretty much considered a standard too. It's ok to not split hairs for vue.js, but then you shouldn't do the same for react...

react-router, do you mean v1, v2, v3, or v4 (or perhaps v5 and v6, I haven't checked if there was a new release with breaking API changes during the past 12 hours).

I'm not a fan of React Router but this sounds like you haven't actually used any of those versions or even looked at the breaking changes.

Here's what actually happened:

v1: https://github.com/ReactTraining/react-router/blob/v3/upgrad...

v2: https://github.com/ReactTraining/react-router/blob/v3/upgrad...

v3 mostly just removed APIs that were deprecated in v2. v3 continues being maintained even beyond the v4.0.0 release.

v4: https://github.com/ReactTraining/react-router/blob/master/pa...

In my opinion it would have been clearer if react-router v4 had been released under a different name but I guess the authors didn't want to pay the cost of that.

The API changes between 1 and 2 as well as 2 and 3 are mostly cosmetic. It's worth pointing out the authors released codemods which will likely be able to convert your app from one version of the library to the next as long as you don't do something exceptionally clever.

The changes between 0.x and v1 were entirely expected. It seems the authors followed the common semantics that 0.x releases are considered experimental, v1 was based on the lessons learned. v2 and v3 then improved upon that design with relatively minor changes.

On the other hand v4 is an entirely new library using an entirely different paradigm: routes use component semantics and are part of the component structure, rather than just some JS router that uses JSX syntax for aesthetics.

But as I said: v3 is still being actively maintained, the authors have just decided that the v4 API fits React better. And for all major releases from v1 to v3 you should be able to upgrade practically for free by using codemods.

I think the importance of codemods can not be understated though many people are still ignorant of them: Facebook releases codemods for every major version of React and uses them internally to upgrade their tens of thousands of components automatically. Third-party libraries like React Router have also started providing them.

Codemods written well should allow app developers to migrate breaking API changes in dependencies with practically no development effort.

Additionally, like React, React Router seems to have adopted the approach of deprecating APIs in the final release of a major version that is no longer going to be supported so you can upgrade your manually code before moving to the new major version with no fear of things breaking. So when upgrading from v2 to v3 you should be able to upgrade safely by simply upgrading to the latest minor version and fixing any deprecation warnings.

Both codemods as well as deprecations of course assume you're doing the sensible thing and a) upgrading one major version at a time and b) actually maintaining your project rather than just spending half an hour on it once a year to implement a new feature with no test coverage.

Personally I often end up doing the not so sensible thing where I end up having to migrate all third party deps to the latest version once a year or two, but libraries like React and React Router are the least of my worries because they are extremely safe and easy to upgrade -- even to the point where there's no need to upgrade beyond React Router v3 unless you also prefer the v4 API.

Re: Switching From React To Vue.js

#140

Post by pluma »

ricardobeat wrote: post #130
buchanaf wrote: post #94

Earlier quoted context omitted.

I mean react-router is almost a 3 year old library trying to handle a rather complex problem. The first three versions were largely the same with no major changes that I can think of except for switching from context to higher order functions. I think everyone is a little dramatic about the number of versions of the library, especially when they are going to continue to support v3.

Well, that just makes things even worse - now you have to choose which version to use, which is just proving the OPs point.

If you don't like having to choose which version of react-router to choose, you probably should be using a preset like create-react-app which makes this kind of decision for you. Or you should use something other than React which includes everything and the kitchen sink.
Post reply on HN