← Back to context Comment by lxgr 19 hours ago Ironically, this seems much faster (for pages already, erm, "researched") than the real one! How? 6 comments lxgr Reply bstrama 18 hours ago 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 lxgr 18 hours ago 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?) bstrama 15 hours ago 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. 1 reply → bstrama 18 hours ago Yep, just a react. Also we use gemini 2.5 flash lite, so it's fast, cheap and dumb. 1 reply →
bstrama 18 hours ago 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 lxgr 18 hours ago 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?) bstrama 15 hours ago 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. 1 reply → bstrama 18 hours ago Yep, just a react. Also we use gemini 2.5 flash lite, so it's fast, cheap and dumb. 1 reply →
lxgr 18 hours ago 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?) bstrama 15 hours ago 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. 1 reply → bstrama 18 hours ago Yep, just a react. Also we use gemini 2.5 flash lite, so it's fast, cheap and dumb. 1 reply →
bstrama 15 hours ago 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. 1 reply →
bstrama 18 hours ago Yep, just a react. Also we use gemini 2.5 flash lite, so it's fast, cheap and dumb. 1 reply →
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.
1 reply →
Yep, just a react. Also we use gemini 2.5 flash lite, so it's fast, cheap and dumb.
1 reply →