@lanodan @NEETzsche @mint

> I think it would reduce the size of debug section if you could just refer to the source code.

It is insanely nice to be able to type 'src cat' and /sys/src/cmd/cat.c is open in the editor. Even something like `go doc -src` is not quite as nice.

> And pain with always distributing source with binaries without any separation is with storage (and mirroring+bandwidth),

Storage was *more* constrained when / was 10MB and /usr got its own 10MB disk, and it still came with source. Source is a blip in terms of storage anyway; I have a packrat /usr/src spanning generations of the OS and it's still just 18GB of space. I keep the source around on the DevTerm and that's a uSD; 4GB of the 128GB card. (It'd be 2GB if I left out qt-everywhere-opensource-src-5.15.11.tar.xz, firefox-119.0.1.source.tar.xz, qtwebengine 6.6, seamonkey 2.53.18, rustc, two versions of qemu, ghostscript.) Source is useful anyway, and you don't have a full system without it: you have a system reliant on a connection to full systems.

> What I guess could be done is more like requiring source to always be installed with binaries, kind of like dependencies are,

That would be fine with me for an OS. But in terms of licensing things I write, I would like to be able to mandate that the source of the actual running thing be made available to anyone using the thing such that it's really trivial to acquire. You know, like, you try to dig up the source for half of these things and they bury it eight clicks down on the website that you got by mashing the software's name into a search engine. I'd like to prevent that ever happening to something I write.