SPA
posts (5)
- Frontend Rendering: from server-side pages to hybrid rendering17/17
Modern rendering is composition
Rendering stopped being a single stage. It is the placement of work across time, space and runtimes, and the framework is a consequence of those decisions.
- 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 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.
- 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…