←back to thread

SourceFS: A 2h+ Android build becomes a 15m task with a virtual filesystem

(www.source.dev)
137 points cdesai | 1 comments | 22 Oct 25 12:39 UTC | HN request time: 0.472s | source
Show context
ongy ◴[22 Oct 25 15:44 UTC] No.45670876[source]▶
While it looks like at least some of the team are ex-googlers, this isn't the srcfs we know from piper (Google internal tools).

Looks like it's similar in some ways. But they also don't tell too much and even the self-hosting variant is "Talk to us" pricing :/

replies(2): >>45671031 #>>45671969 #
jonnrb ◴[22 Oct 25 15:53 UTC] No.45671031[source]▶
WDYM this seems very familiar. At commit deadbeef I don't need to materialize the full tree to build some subcomponent of the monorepo. Did I miss something?

And as for pricing... are there really that many people working on O(billion) lines of code that can't afford $TalkToUs? I'd reckon that Linux is the biggest source of hobbyist commits and that checks out on my laptop OK (though I'll admit I don't really do much beyond ./configure && make there...)

replies(1): >>45671197 #
1. ongy ◴[22 Oct 25 16:04 UTC] No.45671197[source]▶
Oh yea, this is "srcfs the idea" but not "srcfs the project".

I.e. this isn't something battel tested for hundreds of thousands of developers 24/7 over the last years. But a simple commercial product sold by people that liked what they used.

Well, since android is their flagship example, anyone that wants to build custom android releases for some reason. With the way things are, you don't need billions of code of your own code to maybe benefit from tools that handle billions of lines of code.