Miško Hevery

Hydration is Pure Overhead

https://www.builder.io/blog/hydration-is-pure-overhead

The re-execution of code on the client that the server already executed as part of SSR/SSG is what makes hydration pure overhead: that is, a duplication of work by the client that the server already did. The framework could have avoided the cost by transferring information from the server to the client, but instead, it threw the information away.

• older link:
  Minimal Social Markup
• newer link:
  Prevent layout shifts with CSS grid stacks

---

Related contents with similar topics

1. 

   Sam Magura

   Why We're Breaking Up with CSS-in-JS

   • Nicolas Hoizey
   • 3 November 2022
   • JavaScript, CSS, WebPerf
   • 5 reactions

   Thanks for reading this deep dive into runtime CSS-in-JS. Like any technology, it has its pros and cons. Ultimately, it's up to you as a developer…

2. 

   Alistair Shepherd

   Async Alpine — Asynchronous Alpine component loading

   • Nicolas Hoizey
   • 14 October 2022
   • JavaScript, WebPerf
   • 10 reactions

   Async Alpine is a wrapper for the fantastic Alpine.js JavaScript library, giving you greater control of component loading and adding asynchronous/lazy…

3. 

   Harry Roberts

   Speeding Up Async Snippets

   • Nicolas Hoizey
   • 13 October 2022
   • WebPerf, JavaScript
   • 5 reactions

   For all the resulting script is asynchronous, the block that creates it is fully synchronous, which means that the discovery of the script is governed…

4. 

   Joe Liccini

   Why Your Cached JavaScript Is Still Slow and Incurs Performance Overhead

   • Nicolas Hoizey
   • 13 September 2022
   • WebPerf, JavaScript
   • 4 reactions

   Caching assets is a fantastic way to optimize the network overhead of your web application, there is still plenty of computational overhead associated…

5. 

   Joe Liccini

   Why Your Cached JavaScript Is Still Slow and Incurs Performance Overhead

   • Nicolas Hoizey
   • 12 July 2022
   • WebPerf, JavaScript
   • 54 reactions

   Most developers still don't understand that large JavaScript code is really hurting performance, let's hope this great explanation by Joe, that this…