News for hackers. Stuff that matters.
Re:Why Google stores billions of lines of code in a single r... by jsolson on Saturday December 09, 2017 @09:53PM (#15889582)
While technically true due to some features of tooling, that is really only masking off part of the repo under a READ-ONLY directory.

Builds can (and usually do) depend on things that aren't part of your local checkout.

I'd say CitC is a much more accurate representation of the way Piper and blaze "expect" things to work.

Re:Why Google stores billions of lines of code in a single r... by netheril96 on Sunday December 10, 2017 @12:40AM (#15890146)
The dependencies are still downloaded only on need though.
Re:Why Google stores billions of lines of code in a single r... by joshuamorton on Monday December 11, 2017 @10:28PM (#15902792)
The dependencies aren't really "downloaded" at all. When you build something, the artifacts are cached locally, but the files you are editing generally speaking not actually stored on your machine. They're accessed on demand via FUSE.