ooh, there are a couple of statically linked Linux distributions? how do they cope with, say, Firefox?
"oasis uses smaller and simpler implementations of libraries and tools whenever possible:
...
netsurf instead of chromium or firefox...
ah. they don't. that's... pretty much as i expected, tbh
@lily zero link-at-load time; no dependency hell; increased security because of that (nobody can switch in a broken or malicious shared library under your software); potentially lower memory usage; more portable executables... i'm sure there are more, but that's just off the top of my head
@millihertz @lily
> nobody can switch in a broken or malicious shared library under your software
True, but neither can you and if a vulnerability gets discovered in one of the libraries, you'd have to rebuild everything that depends on it — or at least re-link if you keep the object files which no one does, but which would make sense in case with such a distro.
@millihertz @lily
Ha-ha-ha-ha! True — gives away my habit of rebuilding Firefox with my own set of patches, package maintainer mentality 😅
@m0xee @lily the key word is "distro" - the maintainer does the rebuilding, and everyone else just downloads a new copy of the resulting executables. which is how it works now, except for what's downloaded.