Comments by "Immudzen" (@Immudzen) on "The Most Uncomfortable Truths About Linux" video.

That global system library one is definitely an annoying issue. Windows improved a LOT when more applications just had their own copies of libraies locally. On Linux the problem is a big enough issue that we have entire software projects that basically deal with this issue. Things like conda not only create custom python environments they ALSO allow you to have custom libraries for your application separate from the rest of the system. There are also all those tools we use on servers to dynamically swap around environments. This is just so much easier on Windows or Mac by comparison. Each program should be in its own directory with its own bin, lib, etc directories.
34
@lamename2010 when the tradeoff to use shared libraries was made I think it made a lot of sense. It saved on both ram and storage space and both where in short supply but the tradeoff was stability. We now have a lot of ram and storage and the stability tradeoff is not worth it for most libraries.
5
@luckyLaserface I am familiar with the Nix project it is pretty interesting.
2
@la.zanmal. Most programs don't need to be in the path and mostly that just says we need a better way to handle this than a single environmental variable where a whole bunch of directories are shoved into.
2
@insu_na I have experienced using distro provided libraries before and after an update the software I was using broke. The distro changed some compile options for the library and while the version stayed the same it was now missing a feature my software was using. I then had to go through and compile that library by hand and then have the software use that version of the library. It was just a pain in the neck to sort out.
2