Frontend
posts (18)
- Frontend Rendering: from server-side pages to hybrid rendering7/17
SSG: rendering before the user exists
Build-time rendering trades request cost for build cost. You pay once, serve cheaply, and start having a data freshness problem.
- 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 rendering5/17
SSR returns: the server renders HTML again
The server renders the first view not to make the frontend disappear, but to make content exist earlier. The rest of the cost stays on the client.
- 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.
- Frontend Rendering: from server-side pages to hybrid rendering1/17
Server-rendered web: before the frontend became an application
The server assembled a full document for every request and the browser was a document renderer. A simple model, as long as the whole document could be the unit…
- series · 17 parts
Frontend Rendering: from server-side pages to hybrid rendering
A chronology of decisions about when, where and how the UI is produced: from a full document off the server to a composition of build, request, cache…