
I think it’s the comparison to existing systems that falls flat for me. They imply that existing S3-based Git repos can handle, perhaps, hundreds of pushes per second with tens or maybe hundreds of milliseconds of latency. Those are already fantastic numbers that far outpace the needs of even purely agentic workflows. There is already tons of spare capacity.
It feels like trying to sell a car as having a top speed that is faster than the competition when the competition is already significantly faster than the speed limit. If the acceleration or handling is better, then market that. Otherwise it’s a vanity metric.
score 1 · canonical
Oh good to know. I track the uptime of various git forge web hosting and haven’t been impressed by codeberg. But I just switched my test repo over to their git-pages approach. It was pretty easy, did it from my phone.
I’ll see if the migrated test repo has better uptime.
https://alexsci.com/blog/static-hosting-uptime/
score 1 · canonical