The end of 2020 brought a pair of releases that made it look, half-jokingly, like JavaScript had decided to move back to the server: Hotwire from the Basecamp team, and React Server Components from the React team. Both are worth attention, and both are new packaging around ideas that have been around for a while.
What Turbo actually does
Turbo, described as "the heart of Hotwire," grows out of Turbolinks, and its core mechanism is simple. Clicks on internal links are intercepted; instead of a full browser refresh, the contents of the new page are retrieved with fetch, inserted into the current page, and the URL is updated via History.pushState(). The result feels like a Single Page App without the work of building one — which is a good deal if your app already lives in Rails with ERB templates. Hotwire's broader pitch is "HTML over the wire": the server generates and serves HTML, and client-side JavaScript is reserved for what only client-side JavaScript can do.
Is shipping HTML over the wire faster?
Conventional wisdom has held that the network is the bottleneck, so payloads should be as small as possible — usually meaning JSON. But JSON on the client still needs a client-side templating system to become DOM, and that approach carries two costs: loading a client-side library, and the data-to-DOM processing itself. Delivering HTML avoids both, at the theoretical price of a heavier payload — a theory that assumes HTML is heavier than JSON, which is questionable. The honest answer is that it depends on payload size and on what the client is expected to do with the data.
React's server components preview
You might expect React to come down firmly on the client side, but the React Server Components preview doesn't. The accompanying video states plainly that rendering components on the server is faster, especially with nested components that each fetch their own data. What crosses the network is not DOM-ready HTML. Based on the video, it appears to be a proprietary format describing a React component — reportedly "JSON with holes," chunks of JSON separated by whitespace and newlines. That matters because the component need not live in the client-side JavaScript bundle at all, and state can travel in both directions. Lauren Tan notes in the video that this is kinda SSR but distinct from how something like Next.js does SSR today; the goal is to make the Next.js of tomorrow far better.
The state passed to the server is minimal — essentially the current route. The server holds no state.
Because this is React talking to React rather than an open API, the wire format's details matter less, though you may still run into them while inspecting network requests during debugging.
The direction of travel
Servers are simply good at certain jobs, and there's visible momentum toward doing less on the client — which most of us would agree has been taking on a lot lately, with asset sizes doing nothing but growing. The next step is pushing those servers out to the edge.




