3 ms·
The server is only involved when you first hit the page. After that, the client takes care of all the rendering. There is no discrepancy!
by rich_harris 9y ago
The server is only involved when you first hit the page. After that, the client takes care of all the rendering. There is no discrepancy!
- Touche 9y agoThere's a discrepancy if the user doesn't see something when the page first renders but then does see it once the JS runs.
- inventingwithmo 9y agoBut this doesn't happen?
- scottmf 9y agoHonestly these are solved issues. It’s 2018.
- abritinthebay 9y agoThat would be poor coding or application design. There’s no reason for that to happen with SSR. At all. There’s especially no reason for it with modern frameworks like React/Vue/etc - it’s not been a technical problem for years.
- ralmidani 9y agoWith Ember and React at least, it's the same if you use 100% client-rendered elements; the component/template renders to the page, then a lifecycle hook is triggered, and then your custom code/plugin runs.