@emc2 @remmy @0xabad1dea as I understand it, rewriting it was easier than changing the workflow of every engineer in the company and migrating all the infrastructure that had been built on top of it. TBF it did have some genuine quality of life improvements over the original Perforce ("client in the cloud" virtual filesystem etc)
Migration from Perforce to git is pretty painless. I did several such migrations some time back. It's installing a plugin and then running the migration command.
It is certainly less pain than actual *using* Perforce for even a planck unit of time
@emc2 @fraggle @remmy @0xabad1dea id expect serious problems from a single monorepo using git, as it needs the entire repo and all history on every working device.
The solutions to that are a lot harder than just using perforce.
@aliengasmask @emc2 @fraggle @remmy @0xabad1dea This is no longer true. Shallow clones have been available for a long time. More recently it's become possible to limit a clone to specific subtrees, and to update the subtree and history limits later.
MS developed some of that in order to move Windows development onto Git, so there's definitely been some real world success with Git monorepos. (OK, looking at the state of Windows, not that much of a success...)
@bwh @aliengasmask @emc2 @remmy @0xabad1dea even with shallow history, doing a full checkout of google3 is probably infeasible
