Live data from Hacker News

Switching From React To Vue.js

vuejsdevelopers.com

91–100 of 186 posts

Re: Switching From React To Vue.js

#91
post #89

The far biggest problem with Vue for me is the template language. Once you've used JSX you just don't go back to Angular style templates.

A couple notes:

(1) You can use JSX with Vue. https://vuejs.org/v2/guide/render-function.html#JSX

(2) By "Angular style templates" do you mean Vue's Single File Components? Because from my POV they're glorious, and the primary reason I'd be reluctant to use React instead of Vue.

Re: Switching From React To Vue.js

#92
post #63
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…

I switched a reasonably large project and there were many gains with no loss. They've all been said before by me and other people, including in this thread. If you don't see them it's because you don't want to.

[deleted]

Re: Switching From React To Vue.js

#93
post #89

The far biggest problem with Vue for me is the template language. Once you've used JSX you just don't go back to Angular style templates.

Actually the opposite for me, and the original reason I went with Vue (tho after using it more I like a lot about it). I just do not get the appeal of JSX. Directives are meh, but I still prefer it to JSX.

Re: Switching From React To Vue.js

#94

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

Re: Switching From React To Vue.js

#95
post #80

I have built applications using React and most recently Vue2. Both are very very similar and if you are familiar with one you will be able to pick up the other quite easily. In regards to webpages both are capable of doing the same things and fit the same uses cases. That said however if I was to start a greenfield application today, I would choose React. The reason for this is that react is better known, it is easie…

> In a year or two I predict that I will see another article with a title along the lines of "Switching From React To ". It is very unlikely in my opinion that I will see a "Switching From Vue To " article. That might also be because once people get to Vue, they don't leave it for any "new hotness".

Nah, today's hotness is tomorrow's tech debt. Always.

Re: Switching From React To Vue.js

#96

Vue and React both seem a little too heavy in boilerplate. It's also interesting that Vue seems to think that mutable state is a good thing (well, vanilla React does have mutable state too...). For the boilerplate (and large bundle size!) problem we have http://markojs.com that looks very interesting. However, I think what we really might want is something closer to ClojureScript's re-frame ( https://github.com/Day8/…

At the risk of sounding like a shill (I bring up Riot a lot), check out Riot.js. It's a bit rough around the edges in terms of docs/presentation, but it's by far the most minimalistic and most productive "react-like" ui lib I've used.

It's all very very expedient and you can pick it up in a day and be churning out advanced applications with very little mental load. It also supports in-browser compilation so you can get up and running instantly without having to set up Webpack/Browserify/Whatever, which is great for testing it out. Later on you can easily transition to using its offline compiler + whatever packager you want.

The main downside is the community is small. But it's very close to Vanilla JS so I've practically never encountered an issue where I needed riot-specific help.

Re: Switching From React To Vue.js

#97
post #78

What is the state of isomorphic / server side rendering for Vue and React? Is it a straightforward thing to setup?

I haven't done this with Vue yet, but it looks pretty easy to do both prerendering and server-side rendering[1].

A more complete solution, Nuxt.js[2], appears to be gaining in popularity as well.

[1] https://ssr.vuejs.org/en/ [2] https://nuxtjs.org/guide

Re: Switching From React To Vue.js

#99
post #89

The far biggest problem with Vue for me is the template language. Once you've used JSX you just don't go back to Angular style templates.

Actually the opposite for me, and the original reason I went with Vue (tho after using it more I like a lot about it). I just do not get the appeal of JSX. Directives are meh, but I still prefer it to JSX.

Do you think that your preference is just from your previous experience? JSX feels like uninhibited templating to me, which is great when it is done right (and a little crazy when done poorly). I also feel like it gives cleaner error messages.

Re: Switching From React To Vue.js

#100

I have built applications using React and most recently Vue2. Both are very very similar and if you are familiar with one you will be able to pick up the other quite easily. In regards to webpages both are capable of doing the same things and fit the same uses cases. That said however if I was to start a greenfield application today, I would choose React. The reason for this is that react is better known, it is easie…

If we move away from only spa appications vue has other use cases. For a Rails / PHP site that only needs small amount of javascript vue feels like a natural choice to replace some of the existing jquery
Post reply on HN