JavaScript
posts (8)
- Frontend Rendering: from server-side pages to hybrid rendering16/17
Server Components: moving the execution boundary
The rendering boundary stops running through the page and starts running through the module graph. Some components never have a client-side implementation.
- Frontend Rendering: from server-side pages to hybrid rendering15/17
Resumability: what if we don't hydrate at all?
The server records enough information that the client never rebuilds the component tree. Code loads because execution became necessary.
- Frontend Rendering: from server-side pages to hybrid rendering14/17
Islands architecture: interactive fragments in a mostly static document
The starting point stops being the application. The page is a document, and only the fragments that truly need a client runtime get one.
- Frontend Rendering: from server-side pages to hybrid rendering13/17
Selective and progressive hydration: not everything deserves CPU now
Hydration stops being one startup task. Client CPU becomes a resource allocated by priority and by the user's real intent.
- Frontend Rendering: from server-side pages to hybrid rendering6/17
Hydration: connecting HTML with a working application
The server sends the result of rendering, not the application. The browser has to rebuild the component tree and wire it to the existing DOM.
- Frontend Rendering: from server-side pages to hybrid rendering4/17
The cost of shipping the application to the browser
Transfer size is the first cost, not the only one. What counts is the work the device must do before the application becomes usable.
- Frontend Rendering: from server-side pages to hybrid rendering3/17
SPA and CSR: when the browser took over the application
The browser downloads the document once and manages screen transitions itself. The frontend stops being a presentation layer and becomes a long-lived runtime.
- Frontend Rendering: from server-side pages to hybrid rendering2/17
AJAX: the moment a page started behaving like an application
A request stopped meaning navigation. The browser keeps the current document alive and decides for itself what to do with the server's answer.