The irony is that React was supposed to make everything faster...
Netflix: Removing client-side React.js improved performance by 50%
91–100 of 172 posts
Re: Netflix: Removing client-side React.js improved performance by 50%
#92Wow, this is crazy. As a huge vue.js fan I'd argue that the percentage value would be much lower with vue. But, I’m not totally sure.
I'm also a big fan of Vue, but why would it be different in this instance?
Quicker load time but a landing page can be more static. No framework needed.
Re: Netflix: Removing client-side React.js improved performance by 50%
#93I was at the All Things Open conference this week, and Yehuda Katz gave a talk on Glimmerjs[0]. It was enlightening. The size of your front-end application is generally dominated by view code. So, they precompile views into a super simple set of binary VM instructions (making your views very compact). These views don't go through the JS compile / parse phase on the client (saving hundreds of ms, up to seconds on slow…
Why use binary VM instructions with a VM written in JS instead of just straight binary data? Why does it even need to be instructions in the first place?
Re: Netflix: Removing client-side React.js improved performance by 50%
#94Hey, I work on the team at Netflix that gave the talk on React in the signup flow in the tweet. The full talks are available here if people want to watch them: https://www.youtube.com/watch?v=V8oTJ8OZ5S0&t=11m30s Thought I'd also provide some more context on some common questions that people have asked. ### Why are you using React to render a landing page? The Netflix landing page is a lot more dynamic than most peop…
It is quite telling that you give the example of the component which has "one or two checkboxes on the UI" that "has some of the most complicated logic in the codebase".
Re: Netflix: Removing client-side React.js improved performance by 50%
#95Today we learned: Removing an advanced library from a simple project increases performance. Sorry for being sarcastic but don't you also find this too obvious?
> Sorry for being sarcastic but don't you also find this too obvious?
If we pay attention to how bloated most web pages are, it seems it is not obvious at all.
Re: Netflix: Removing client-side React.js improved performance by 50%
#96Hey, I work on the team at Netflix that gave the talk on React in the signup flow in the tweet. The full talks are available here if people want to watch them: https://www.youtube.com/watch?v=V8oTJ8OZ5S0&t=11m30s Thought I'd also provide some more context on some common questions that people have asked. ### Why are you using React to render a landing page? The Netflix landing page is a lot more dynamic than most peop…
Split code by routes?
Split interactions and the view layer?
fiber?
Stream the render?
Re: Netflix: Removing client-side React.js improved performance by 50%
#97The irony is that React was supposed to make everything faster...
Actually you are incorrect, not everything, but the most important part, development time.
Re: Netflix: Removing client-side React.js improved performance by 50%
#98I was at the All Things Open conference this week, and Yehuda Katz gave a talk on Glimmerjs[0]. It was enlightening. The size of your front-end application is generally dominated by view code. So, they precompile views into a super simple set of binary VM instructions (making your views very compact). These views don't go through the JS compile / parse phase on the client (saving hundreds of ms, up to seconds on slow…
Wow that site loads instantly
It's a tiny page of static html.
Re: Netflix: Removing client-side React.js improved performance by 50%
#99Hey, I work on the team at Netflix that gave the talk on React in the signup flow in the tweet. The full talks are available here if people want to watch them: https://www.youtube.com/watch?v=V8oTJ8OZ5S0&t=11m30s Thought I'd also provide some more context on some common questions that people have asked. ### Why are you using React to render a landing page? The Netflix landing page is a lot more dynamic than most peop…
Split code by routes? Split interactions and the view layer? fiber? Stream the render?
So just keep throwing more shit at it till it gets faster?
Re: Netflix: Removing client-side React.js improved performance by 50%
#100Well, of course it will. You are trading loading an entire application for loading a static page. I'm always amazed at those devs who load entire applications framework when their end goal is to have a slider at the top of a page.
"static page"