JavaScript
posts (13)
- The Layers of HTTP in the Browser: From fetch() to QUIC1/9
Request and Response: What Does the Browser Actually Send?
A request is not a URL, and an HTTP response is not always JSON. Headers and body have separate lifecycles, and an HTTP error is not a network failure.
- 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.
- Realtime in the Browser: From Polling to WebTransport4/7
Server-Sent Events: An Event Protocol over HTTP Streaming
A standard event format and reconnection on top of an HTTP stream. Last-Event-ID gives you resume, but it does not solve event durability in the system.
- 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.
- Ways of Talking to a Backend: From HTML Forms to GraphQL3/6
Fetch API: The Modern Browser Interface to HTTP
fetch did not change the communication model, only the interface. Request and Response are objects, the body is a stream, and a 404 is not an error.
- Ways of Talking to a Backend: From HTML Forms to GraphQL2/6
AJAX: When a Request Stopped Meaning a Page Reload
XHR did not change the protocol, only the reader of the response. Status, headers and the origin boundary stopped being the browser's business and became the…
- series · 6 parts
Ways of Talking to a Backend: From HTML Forms to GraphQL
The layers of frontend to backend communication from the bottom up: forms, XHR and fetch start the request, HTTP carries it, and REST, RPC and GraphQL model…
- 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.