It generates articles only once. So once it's generated, it never perish. Logic looks like: If article exist -> show it If not -> generate and save

I get that, but how does it serve the generated and cached ones seemingly faster than Wikipedia? (My guess is that single-page applications, which this one seems to be, just need less round trips between navigations or something?)

Also now that I think, we store articles in decwntralized cloudflare KV store and access from serverless workers running also on their servers.

That could be the thing behind it being so quick.

Cloudflare workers have 1ms cold start.

Nice job, this is seriously one of the fastest websites I've ever used!

I feel like I have some minimum latency "priced in" to my expectation when I click a link on a static site, so yours feels uncannily like it's somehow able to anticipate my clicks, adding to the surreal atmosphere.

Yep, just a react. Also we use gemini 2.5 flash lite, so it's fast, cheap and dumb.

Nice, that's what I used for by LLM-backed HTTP server [1] a while ago as well :) It's a shame they got rid of the generous free quota a while ago, which is why I had to shut my public instance down.

[1] https://github.com/lxgr/vibeserver/