4 ms·
The problem with many of these tools is they are built on lots of other tech, like S3 dev called out: https://x.com/haipingfu/status/2084880266858995990 https:/
by kyrra 1mo ago
The problem with many of these tools is they are built on lots of other tech, like S3 dev called out: https://x.com/haipingfu/status/2084880266858995990 https://x.com/haipingfu/status/2084880266858995990
Piper is built on lots of other tech like spanner and chubby and many others. And some of those have specific hardware requirements that only exist in Google datacenters. Untangling that web of tech is neigh impossible (or not something worth the cost to leadership).
- fragmede 1mo agoWhy is that a problem? They sell Spanner on GCP. Sell Piper as well! It's obvious as shit but Google doesn't know what it's doing anymore. They should have bought GitHub, not Microsoft, and then we wouldn't have had the problems with scaling GitHub either.
- kyrra 1mo agoPiper only works with CitC. Which is effectively a virtual file system when mounted locally. And when you have a monorepo that big, standard tools that want to scan an entire directory will stop working. Every part of the developer tool chain has to change to deal with code base that big. I agree that Google should have bought github. The tech they built to scale Google Code I think would have helped a ton with GitHub.
- fragmede 1mo agoThey sell and support Google Drive on Mac and windows, and the web. Selling a VFS layer is entirely within their capabilities. Blaze/Bazel has already been exported. You're right that there's a whole stack, but if Facebook can make jj happen, Google could make hg happen.