[SBArbeit]

The fact that most of your Git commands are local-only is an artifact of how Git works, but I expect that ~100% of the time, you have an internet connection, so the fact that Grace needs to be connected to the cloud just isn't a thing I worry about.

I'm not writing a new VCS based on the 0.00000001% "but I'm on an airplane without WiFi" case.

There's ~0% reason in 2024 to build software for offline use cases, and even less reason in 2026 and 2028. I'm happy to cede that to Git if you really need it.

As an industry, we fetishize offline for version control only because Git sort-of does that. Again, it doesn't really... you still have to push to do real work with your team, but we need to stop pretending that's a hard requirement. It's totally not, it's just a "feature" of Git that gets in our way today more than it helps us.

> Also I once had a case of working on an air-gapped network.

Coming from Microsoft, and being familiar with the air-gapped Azure instances for government, I designed Grace to be able to run on those Azure clouds. In other words, all of the PaaS services that Grace would use on Azure are present in those clouds.

Even the air-gapped world isn't "offline", it's totally networked, just on a network that's not connected to the Internet.

I haven't specifically looked at similar AWS instances, but I have to believe it's possible there, too.