@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 git would be a legitimately bad choice for what Google are doing - you can’t have everyone needing to pull every change anyone in Google made to get the one change they do care about in a subset of that. Also distributed version control makes no sense in a company where to my understanding it’s not permitted to have source checkouts on your local device.
