News for hackers. Stuff that matters.

A comment on Improving large monorepo performance on GitHub. Parent comment

Re:Improving large monorepo performance on GitHub by jayd16 on Tuesday March 16, 2021 @03:39PM (#26481805)
I thought Google used some custom fork of perforce.
[ Parent | on HN ]
Re:Improving large monorepo performance on GitHub by klodolph on Tuesday March 16, 2021 @04:46PM (#26482712)
From what I understand, Piper is not a fork of Perforce, but instead a completely different system with the same interface. You know, built on top of a BigTable or Spanner cluster instead of whatever Perforce uses.

The Mercurial extensions are then an alternative client for Piper.

[ Parent | on HN ]
Re:Improving large monorepo performance on GitHub by dlp211 on Tuesday March 16, 2021 @08:56PM (#26485269)
It's my understanding that it started as a fork of perforce, Google bought a source license for perforce. Whether you'd still call a fork of perforce anymore is like asking if a Computer is the same computer after you've replaced all the components over the years.
[ Parent | on HN ]
Re:Improving large monorepo performance on GitHub by arthurdenture on Tuesday March 16, 2021 @11:29PM (#26486183)
That was the case many years ago (extremely customized perforce server), but after that there was a full rewrite as a distributed system built on Bigtable etc. - https://cacm.acm.org/magazines/2016/7/204032-why-google-stor... is an overview. It wasn't a ship-of-Theseus type situation where they incrementally replaced components.
[ Parent | on HN ]