3 ms·
After this, we will get back to shared libraries, because updating that libpng would require updating all those static binaries. This is already happening with
by dig1 5y ago
After this, we will get back to shared libraries, because updating that libpng would require updating all those static binaries. This is already happening with many go and rust programs.
- guhidalg 5y agoNo? Assuming all processes on a machine _want_ to use the same shared library is what leads to isolation mechanisms.
- ReptileMan 5y agoNo need anymore. Both bandwidth and storage are dirt cheap. Linked libraries became obsolete the moment hard drives became huge.
- still_grokking 5y agoOnly if you don't care about security.
- teknopaul 5y agoAnd became relevant again the moment people stopped using HDs in devices that run Linux ;)
- AnIdiotOnTheNet 5y agoAnd eventually maybe it'll all converge back to the rational way to do things: a base set of shared libraries provided by the OS that maintain strict ABI compatibility, and everything else static.
- snovv_crash 5y agoRight until you want to run more than one release on the same machine...
- hackeraccount 5y agoI think the end goal is what we all want - be able to do any of the options - single binary to external libraries and anything in between easily. Not with the one way going in fashion and the other out but both supported and accessible.