Browser APIs
posts (5)
- Frontend Rendering: from server-side pages to hybrid rendering12/17
Edge rendering: compute moved closer to the user
Moving compute closer to the user only pays off when the data travels with it. Otherwise we shorten one hop and lengthen the rest.
- 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…