Deleted Comment
Helsinki has about 3x fewer vehicles per capita than the average U.S. city. So it’s not surprising it’s safer since fewer cars mean fewer chances of getting hit by one. Plus their cars are much smaller.
In fact, there are probably plenty of U.S. towns and cities with similar number of cars that have zero traffic deaths (quick search says that Jersey City, New Jersey has zero traffic deaths in 2022).
So maybe it’s not about urban planning genius or Scandinavian magic. Maybe it’s just: fewer things that can kill you on the road.
I wonder how the numbers will change when majority of cars are autonomous.
Deleted Comment
It is a requirement because you can't find GPUs in a single region reliably and Kubernetes doesn't run on multiple regions.
>> * Tailnet as the default network stack
> That would probably be the first thing I look to rip out if I ever was to use that.
This is fair, we find it very useful because it easily scales cross clouds and even bridges them locally. It was the simplest solution we could implement to get those properties, but in no way would we need to be married to it.
>> * Multi-tenant from the ground up
> How would this be any different from kubernetes?
Kuberentes is deeply not multi-tenant, anyone who has tried to make a multi-tenant solution over kube has dealt with this. I've done it at multiple companies now, its a mess.
>> * Bittorrent as the default storage stack
> Might be interesting, unless you also mean seeding public container images. Egress traffic is crazy expensive.
Yeah egress cost is a concern here, but its lazy so you don't pay for it unless you need it. This seemed like the lightest solution to sync data when you do live migrations cross cloud. For instance, I need to move my dataset and ML model to another cloud, or just replicate it there.
How so? You can definitely use annotations in nodes and provision them in different regions.