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

Vue 3.0 Updates [slides]

docs.google.com

Post reply on HN
Print view View original

61–70 of 126 posts

Re: Vue 3.0 Updates [slides]

#61

Post by GordonS »

Illniyar wrote: post #49
TekMol wrote: post #39

Earlier quoted context omitted.

When the user triggers a change of the underlying data, I do a roundtrip to the server and re-render the current page. I keep the time needed to do so under a second. My users regularely express how WOWed they are by the snappyness of my sites. I guess what other sites save on re-rendering html, they lose multiple times on bloated code.

That literally means that you aren't doing SPAs. If you aren't doing SPA then yes using React or Vue is rather a waste. However the majority of sites these days use some form of SPAs. Also under a second is a very low bar to strive to. a fast round trip to the server is 100ms. A reasonable one is somewhere around 300ms. Displaying effects to changes is often under a millisecond in SPAs and is basically impossible to…

> However the majority of sites these days use some form of SPAs

Do you have a reference for that claim? I very much doubt you are correct, but I'd be interested in seeing some stats either way, if they exist.

Re: Vue 3.0 Updates [slides]

#62

Post by williamdclt »

k__ wrote: post #45
eksemplar wrote: post #34

Earlier quoted context omitted.

Having started with vue, and now playing with react, I’ve found myself often thinking “this is so much simpler”. But maybe I just sucked at vue.

I think two-way-binding is the reason why many people prefer Vue to React. If you did Ember or Angular1, Vue is much easier to grasp.

Well, one-way binding (or rather, unilateral data flow) is why I prefer React :)

Re: Vue 3.0 Updates [slides]

#63

Post by bsaul »

bpicolo wrote: post #40

The Typescript support is by far the thing I'm most interested in. Lack of useful Typescript support is, for me, the only downside of Vue right now, and it's a big enough downside for me to use React instead of Vue in a lot of cases. Do you reckon we'll ever see Typescript support in the non-jsx templates? I do really like vue templates for e.g. if-conditionals. I really don't like using ternary operators for templat…

to me the biggest downside was how vuex and typescript didn’t work well together by default. You had to rely to adding a few plumbing functions, and that felt really like dirty patching.

Re: Vue 3.0 Updates [slides]

#68

Post by orf »

welanes wrote: post #65

.

FYI it takes 5.16 seconds to download the 5 megabytes of vendor JavaScript needed to view your landing page from a cold cache (and 2 for your app itself), not to mention the 6 seemingly needless Firebase API calls or the fact you're running the development version of the Firebase SDK.

No matter how awesome you think whatever framework is, this is a terrible, terrible experience.

Re: Vue 3.0 Updates [slides]

#69

Post by Normal_gaussian »

Slide 20 "flow -> typescript" is under making it more maintainable - does anyone have any thoughts on this?

I use flow because I am interested in soundness, have had a few issues with it, but nothing has suggested to me that typescript is more maintainable.

Re: Vue 3.0 Updates [slides]

#70

Post by um_ya »

keerthiko wrote: post #11
shabbyrobe wrote: post #6

Earlier quoted context omitted.

What power does React offer you that Vue can't? It'd be quite interesting to hear your take on it.

Exporting reactive JS native apps for iOS and Android is the most significant feature -- was what I would have said. I looked it up before writing this comment, and apparently Vue introduced this in June 2018. Case in point of this comment thread :)

With vue native you can use anything from the react native community in a vue application. You get the best of both worlds!

https://vue-native.io/

Post reply on HN