> you should at the very least give us a hint as to why you're doing that Well, they did. In the very thing you quoted: > On Medium, we speed this up a bit w

> you should at the very least give us a hint as to why you're doing that Well, they did. In the very thing you quoted: > On Medium, we speed this up a bit with JavaScript. [...] format=json," download the article text eg, they send what actually changed, probably highly compressed and cached, and not an entire new webpage. That's not super uncommon, and it's hardly weird or roundabout. We can discuss whether they've correctly identified the bottleneck (although, spoiler, they have), or whether it actually improves things for their users in real world conditions (probably), or if the technical overhead is worth it for something like Medium (debatable, but apparently they have the funding...), but it's not "bizarrely strange". It's a well known technique, and while maybe it's more common (and more sensible) to use it on a webmail app than a weblog, it's not black magic.