Transcript from the "Why Use Universal Rendering?" Lesson
>> Brian Holt: We're gonna move on to universal rendering. So, taking our app, rendering it on the server first, and then sending it down the wire. So, let's discuss why you wanna do that, cuz it sounds like a whole lot of extra work. So, if I open my View Source here, View Page Source.
>> Brian Holt: Yeah, cuz I have to run dev again.
[00:01:23] Like on shitty hotel Wi-Fi, or you're in 2G, or you're in a foreign country that has really bad Internet access. These are all common use places, right? So, what we want instead is we want to send down the complete markup first for this initial page. So, this markup appears before someone instantaneously, right?
[00:01:45] Then they look at this page, right, it's gonna take me at least a second to discern. Okay, brand, okay, search. Okay, now I can search for a movie. So I'm gonna search for house, right? It's gonna take me a least a couple seconds to put all those things together.
[00:02:25] And then, React is gonna hurry and bootstrap behind the scene. So any question about the process and why we want to do universal rendering? So we want to send down complete mark-up. That's the point of universal rendering. So, it's gonna send down this mark up. This mark up is not going to be interactive, right?
[00:03:25] So, we have a node server that sits in front of our Java servers that then serve requests to people. So, people make requests against the node. We do all of our server side rendering on our node server and then we send it back down. And our node server is actually what talks to all of our different services.
[00:03:41] So, if you're on Python or Django or Ruby or anything like that, that's how you're gonna have to do this if you want to do this, which you should, I think.