Open azamat-sharapov opened 9 years ago
@azamat-sharapov hey! Wow, it's a bit of surprise you stumbled into it :) Though I've just planned to translate the presentation and yes, we're already working on moving VueServer.js to open source.
Great, thanks! Video was shared by vue.js team on vkontakte, so I noticed it and took my time watching. It's good to see Vue was chosen for a huge project like yours, makes me more confident that Vue will work for my big projects also.
@azamat-sharapov A group about vue.js in VK? Amazing! Didn't know there were any of those :D Aye, Vue.js do well in a large scale project. We're not having any serious problems with it.
@yyx990803 are you with us? I'm getting slides tranlated and wondering, are you interested in english subtitles for the report video?
@fullfs Yeah, totally!
Well, here we go with slides: https://www.dropbox.com/s/f5e7zctsca0fv6w/Rendering_is_fit_for_more.pdf?dl=0
By the way, React server side rendering time measurement I did were a bit incorrect. One should run React on node.js with NODE_ENV=production
. It makes React to run about 4 times faster.
Very cool! Thanks dude!
Re: React production mode: you should be using the minified production build of React in browser tests too. That makes its hot updates (re-rendering the whole list) like 3x faster. But talking about hot updates.... since your components don't really have private state, you should use track-by="$index"
which makes even bigger difference (down to 25ms re-renders) ;)
Oh, yeah, I see the difference now. Though Vue.js initialization time is still better than React.
And wow, track-by="$index"
is amazing! Didn't know there were such a feature :) The time is at least 2 times better than React in production mode!
Interesting stuff. I'm interested to learn more about Vueserver.js as well.
Interesing me too. :smile:
me too!
Oh, well... Let me say a few words about VueServer.js then. Now I've got 2 versions of the module: for Vue.js v0.11.* and for v.12.* The second one is in beta state now. Also there are some flaws:
<content>
tag components mounting system is not supported by now.wait-for
or other reactive-bases features, but there are also some restrictions. In our project we don't have any problems with it by now, but it's the result of our project developing way. In other projects there is definetly a possibility to meet some wtf? why is it not working on server, but in browser it's ok?
And yeah, the code base is a bit of mess right now :D
@fullfs Thanks !! I'm looking forward to VueServer.js is published as open source.
Interested in this too!
Wow! The numbers with Vue.js server are great, the Seo capability it's nice too! Looking forward to see VueServer open source :+1:
here is another project that may help with DOM on the server https://github.com/patrick-steele-idem/morphdom/
@fullfs hey there, awesome stuff. Any updates on the state of VueServer? Also, can you talk a bit about how it works (internal stuff)? Thanks!
@alessioalex Sorry, nothing yet. Was just on vacation for several weeks
@fullfs don't know if this is relevant, but here's the Angular 2 presentation on their approach to the problem: https://www.youtube.com/watch?v=0wvZ7gakqV4
Hey @fullfs what's up?
I've watched your presentation other day, great talk! Any chance you could have your slides translated or put somewhere, so we can translate? Mainly Vue.js related part. @yyx990803 is also interested. We are also wondering, if you could open source VueServer.js, if possible :)
See this tweet.