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

81–90 of 186 posts

Re: Switching From React To Vue.js

#81

Post by coldtea »

danmaz74 wrote: post #29
mcintyre1994 wrote: post #22

Earlier quoted context omitted.

https://vuejs.org/v2/guide/routing.html For most Single Page Applications, it’s recommended to use the officially-supported vue-router library. For more details, see vue-router’s documentation. https://github.com/vuejs/vue-router -- https://vuejs.org/v2/guide/state-management.html Vue offers vuex: our own Elm-inspired state management library. https://github.com/vuejs/vuex -- Out of the box or not, they're part of th…

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

>And react-router, while not being on the same github, is pretty much considered a standard too.

The kind of standard that just doesn't stop giving backwards incompatible BS releases...

Re: Switching From React To Vue.js

#82

Post by coldtea »

amauta wrote: post #65
k__ wrote: post #35

Things you're sacrificing when going away from React: 1. Stability. FB uses it for their main product, which is probably the biggest web app of them all, they pay many devs to work fulltime on it. People coming from Angular, who had to migrate all those breaking changes over the years know the struggle. 2. Options like React-Native, React-VR and co. React enables your devs to acquire a whole new range of possibilitie…

Vue is backed by one of the biggest companies in China and many Chinese startups.

Well, and lots of Western startups from what I gather...

Re: Switching From React To Vue.js

#83

Post by coldtea »

thejosh wrote: post #37
k__ wrote: post #35

Things you're sacrificing when going away from React: 1. Stability. FB uses it for their main product, which is probably the biggest web app of them all, they pay many devs to work fulltime on it. People coming from Angular, who had to migrate all those breaking changes over the years know the struggle. 2. Options like React-Native, React-VR and co. React enables your devs to acquire a whole new range of possibilitie…

Its what they use right now, who knows what is coming down the pipeline?

Nobody. But the fact that they use it now makes it less likely to be abandoned by them that something they don't use (which, while they can't abandon, they haven't adopted either).

Besides in 10 years the whole of IT changes. Don't look for "50 year frameworks".

Re: Switching From React To Vue.js

#84

Post by alttab »

__BrianDGLS__ wrote: post #47

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…

I read through the differences, and they seem small enough that for any decently sized project with a non-trivial team you'd choose React and in most cases probably not even consider Vue.

Re: Switching From React To Vue.js

#85

Post by codazoda »

I stopped reading at "both are fast and light weight" because I don't find react to be "light weight". React is 275K (nearly a quarter of a meg) when it is minified and gzipped. 750K when it is not minified/gziped.

We're talking about a web page UI here. It should be tiny for users with slow connections. React seems big to me and I can't justify it except in very large applications.

As such, I struggle to find the reason React is so popular. Perhaps I'm a bit old school. People say it's easy to reason about, but I don't find that to be true in real world large applications with a lot of developers working on them.

Still, I'm trying to like react, but these things are a struggle for me.

Re: Switching From React To Vue.js

#86

Post by beager »

TekMol wrote: post #14
madeofpalk wrote: post #7

Earlier quoted context omitted.

Mobile Twitter uses React. https://mobile.twitter.com/facebook Airbnb uses React https://www.airbnb.com.au/rooms/432044 Facebook, Facebook Messenger, Instagram, Netflix, Reddit Mobile, new Reddit Profile pages are all high profile sites using React that aren't just 'backend dashboards'.

Interesting. The ones not behind a login (Twitter,AirBnB,Reddit Mobile) are sites that feel laggy and clunky to me. With slow loading content, loading animations, laggy scrolling, too much stuff opening in new tabs, confusing interfaces. I wonder if React causes/incentivises this or if it's design decisions by the coders/designers/managers. In contrast, pages like Reddit Desktop, Google and Amazon work much better fo…

I don't contest that those sites feel laggy and clunky, whether by poor load time, poor UX/UI, or some larger dysfunction.

However, I would offer that the usage of React is not so much the cause of poor performance but rather a step taken to remedy scale lag. Large apps like the one you mention are big behemoths that take months to adopt new architectures and patterns, but those activities are required to ensure the scalability of the infrastructure and product development. During the time those apps are not fully transitioned to React (and Redux, and isomorphic rendering, and a fully-featured API, and webpack, and a litany of other tools), they might feel half-baked or sluggish, because you may have a page loaded with server-side template rendering, but half of your components on the page are upgraded to React, and take a second to initialize.

IMO, React is a tool that provides an appropriately rigorous rubric for component development and a structure for large-scale interplay of reusable/composable frontend components, which was required for it to have any viability for a large org like Facebook. A lot of web apps are on the long trek to avail that potential fully, but while they're in transition, the experience of those apps will be a little disjointed or degraded.

Re: Switching From React To Vue.js

#87

Post by k__ »

TekMol wrote: post #68
k__ wrote: post #35

Things you're sacrificing when going away from React: 1. Stability. FB uses it for their main product, which is probably the biggest web app of them all, they pay many devs to work fulltime on it. People coming from Angular, who had to migrate all those breaking changes over the years know the struggle. 2. Options like React-Native, React-VR and co. React enables your devs to acquire a whole new range of possibilitie…

Options like React-Native When you use React for a web app, how close are you to turn it into a React Native app?

I'm a freelancer, so I do different projects. Web, Mobile, etc.

Now I can do them all with one framework.

Re: Switching From React To Vue.js

#88

Post by nightski »

sheeshkebab wrote: post #58
nip wrote: post #25

Earlier quoted context omitted.

Is it because of the technology or because of the team? Rhetorical question - I am by no means attacking you or your team, I just clicked on your "is messy with JSX, router" sentence and decided to put my reply under yours. I see many people tackling React but not developing in a 'React' way. For example I recently saw on HN some user complaining that he had to create N functions to handle N items on a form, while co…

router and redux make it messy (or rather lack of standard of routing and global state management in react makes every one create their own half assed implementations)... also transitioning web developers from writing giant HTML pages to thinking about smaller components is a difficult, without dedicated react designer. All these make non trivial react apps a graveyard of crappy jsx and messy untyped tangles of JavaS…

I'd be really surprised if the team you had producing this huge mess was all of a sudden producing super clean code in Vue. It sounds like a very inexperienced team. Probably would be worth investing in a senior developer or team lead to help guide these fresh devs.

Re: Switching From React To Vue.js

#90

Post by __ddd__ »

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.

JSX is very close to HTML. Maybe the issue is expecting designers who have zero dev skills to build front ends in a time of responsive design and rich JS interfaces. You wouldn't hire a print designer with no Photoshop experience to design a site, and you shouldn't hire a graphic designer with no web dev skills to build front ends. If you're team is really well formed, you might have an experienced graphic designer, a UX expert, and a front end developer who does the actual building as well as making day-to-day design decisions. The design/interface experts would work at a higher level of creating an overarching design language and UX guidelines.
Post reply on HN