3 ms·
This is exactly as I'd expect. If you want a centralized, trunk-based version control, don't use git. It's funny how each company decides to solve these probl
by anon9001 5y ago
This is exactly as I'd expect.
If you want a centralized, trunk-based version control, don't use git.
It's funny how each company decides to solve these problems.
Google called in the computer scientists and designed a better centralized vcs for their purposes. Good on them. It'd be great if they open sourced it. So typical of Google to invent their own thing and keep it private.
Microsoft took the most popular vcs (git), and inserted a shim layer to make it compatible with their use case. How expected that Microsoft would build a compatibility shim that attempts to hide complexity from the end user.
Meanwhile, Linux and Git are plugging along just fine, in their own separate repos, even though many people work on both projects.
- IshKebab 5y ago> So typical of Google to invent their own thing and keep it private. Yeah like their build system... Bazel, that's completely closed source.
- erik_seaberg 5y agoGoogle did not design a VCS from scratch, they adopted Perforce and started replacing its backend as they hit scaling limits. They eventually added some kind of copy-on-write FUSE layer that looks like your workspace contains the entire monorepo, which was pretty cool. It would be hard to open source if its dependencies only exist on Borg. I think that was a problem with Blaze (now Bazel).