JavaScript hydration — the process of reattaching interactivity after server-side rendering — has long been a performance bottleneck for web frameworks. Ryan Carniato traces the journey that led the Marko team and Misko Hevery (creator of Angular and Qwik) to independently arrive at 'resumability': a technique where the server

6m read timeFrom playfulprogramming.com
Post cover image
Table of contents
Finding Resumability Copy link Link copied!Eliminating Hydration? Copy link Link copied!Hydration is a Solved Problem Copy link Link copied!

Sort: