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

111–120 of 186 posts

Re: Switching From React To Vue.js

#111

Post by fonybalony »

codazoda wrote: post #85

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 re…

> React is 275K (nearly a quarter of a meg) when it is minified and gzipped. 750K when it is not minified/gziped.

That statement is completely false.

react@15.5.4:

react.min.js is 21335 bytes uncompressed, 7353 bytes gzipped.

Re: Switching From React To Vue.js

#112

Post by literallycancer »

TekMol wrote: post #6

What are good examples of popular websites (not behind a login) that make use of Vue or React? I ask because I keep reading about it, all programmers seem to use it, but I just don't come across websites that use it. Is it only used for backend dashboards? Or do all Vue/React sites fail to gain traction for some reason?

Here you go https://wappalyzer.com/applications/vue-js (first page of google results)

From what I understand, Vue is quite popular with the laravel community.

Re: Switching From React To Vue.js

#113

Post by literallycancer »

matt4077 wrote: post #45
TekMol wrote: post #14

Earlier quoted context omitted.

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 know why you're arbitrarily dividing the data into "behind a login" and, well, "not". I doesn't make any difference. For the rest: opening in tabs is obviously a design choice. So are "confusing interfaces"–whatever that may mean, because if those reddit and twitter mobile sites are confusing you, good luck with amazon. React build a DOM. You can make a table-based layout with a spinning e-mail icon if that's…

Presumably he wants to see more than just the landing page and doesn't want to bother registering.

Re: Switching From React To Vue.js

#115

Post by deskamess »

swsieber wrote: post #72
yunyu wrote: post #41

Earlier quoted context omitted.

That approach is actually heavier - the template compiler needs to be distributed (extra 15kb gzipped) and templates need to be rendered at runtime.

I think they meant "lighter integration" - you need less tooling to get going. Bad for performance, but good for dipping your toes in. But that is important to note - it's not the most performance way to do it.

Correct... I was referring to the tooling ecosystem.

Re: Switching From React To Vue.js

#116

Post by jaequery »

There is a bit of React kool-aid in here, makes me really wonder if any of them have actually tried using Vue because the benefits and improvements you will see with Vue are immediately noticed.

To be frank, the OP actually did a poor job of presenting Vue here because it only mentioned the similarities, which doesn't do any good for Vue. It did not get into areas where Vue is better than React, which is what most would be interested in hearing.

If you ever put React and Vue.js side by side and compare, it is almost a no brainer to switch. How it handles bindings, the way they got Redux done right, and the single file component style, are all improvements over React IMO. I'd jokingly say if React were to keep improving and evolving for the next couple years, it may possibly look like Vue.js as of today.

Re: Switching From React To Vue.js

#117

Post by speg »

jaequery wrote: post #116

There is a bit of React kool-aid in here, makes me really wonder if any of them have actually tried using Vue because the benefits and improvements you will see with Vue are immediately noticed. To be frank, the OP actually did a poor job of presenting Vue here because it only mentioned the similarities, which doesn't do any good for Vue. It did not get into areas where Vue is better than React, which is what most wo…

Interesting. I hadn't touched React in months and recently spent a week with Vue. I had trouble getting up and running and was soon longing for React, or at least what I remembered of it.

Re: Switching From React To Vue.js

#118

Post by hashkb »

jaequery wrote: post #116

There is a bit of React kool-aid in here, makes me really wonder if any of them have actually tried using Vue because the benefits and improvements you will see with Vue are immediately noticed. To be frank, the OP actually did a poor job of presenting Vue here because it only mentioned the similarities, which doesn't do any good for Vue. It did not get into areas where Vue is better than React, which is what most wo…

I'd love to see you elaborate. Your post is just Vue Kool aid.

Re: Switching From React To Vue.js

#119

Post by coldtea »

c0achmcguirk wrote: post #95
coldtea wrote: post #80

Earlier quoted context omitted.

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

In JS maybe. But I don't think there's anything fatalistic about it. There are still C, C++, Lisp, even Pascal etc codebases maintained and liked just fine.

It's about maturity and churn, not something inherent in programming.

Re: Switching From React To Vue.js

#120

Post by codazoda »

fonybalony wrote: post #111
codazoda wrote: post #85

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 re…

> React is 275K (nearly a quarter of a meg) when it is minified and gzipped. 750K when it is not minified/gziped. That statement is completely false. react@15.5.4: react.min.js is 21335 bytes uncompressed, 7353 bytes gzipped.

I'm including everything you need to deploy in those numbers. You included only React and not React-Dom. My own try at setting up React results in a 750k js file when I follow the instructions below. I realize this isn't minified yet and I welcome feedback on how to make it better.

https://www.joeldare.com/blog/post/create-a-react-app/

The top search results for react minified size show similar numbers to my 250k. There are a lot of people throwing out a lot of numbers that are different. Versions likely play a role, especially after 15. Here are some references.

https://gist.github.com/Restuta/cda69e50a853aa64912d

https://stackoverflow.com/questions/19807946/why-is-reacts-f...

Nothing I can find references a size as small as you mention with react and react dom. Most recommend writing with ES2016 which probably adds Babel overhead as well. When I build "Hello World" myself, I can't get anywhere near the small sizes.

I'd love someone to give me a proper smack-down on this. I want to love React since it's a recent requirement of my job. But with my current knowledge of it, I can't seem to get the size down.

Post reply on HN