6 ms·

> cloud-native version control Just how "cloud-native" are we talking here? One chief selling point of git is that you are not reliant on a centralized server.

> cloud-native version control Just how "cloud-native" are we talking here? One chief selling point of git is that you are not reliant on a centralized server. You have remotes, yes, but if one of them goes down, you still get the entire project history. I am of the opinion that the software world needs to find something better than git. One of my major pain points as a lead are the inevitable, yet unpredictable, git questions I will be getting from new juniors. But "cloud native" sounds like a poor starting point for "better git". Not needing external servers for VCS is one of the things git gets right.

sasham 3y ago
> Just how "cloud-native" are we talking here? So we're entirely serverless, using distributed cloud storage and DBs. Basically Diversion is up as long as you don't have a major AWS outage (happens, but rarely). > Not needing external servers for VCS is one of the things git gets right. I agree in general. But the way most devs are using git today isn't really decentralized, everything is going into and out of GitHub/Lab. And the more often the better, because CI and merge conflicts. So I wonder if having a VCS that is decentralized in theory really important - taking into account the upsides of building in the cloud (scalability, distribution speed, collaboration etc).