Hacks by Mekineer

User Tools

Site Tools

You are here: decentralized encyclopedia » information technology » 2018 portable software
information-technology:2018-portable-software

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
information-technology:2018-portable-software [2024/02/22 04:15] – [2018: Portable Software] marcosinformation-technology:2018-portable-software [2026/01/07 00:31] (current) – marcos
Line 1: Line 1:
- 
 ====== 2018: Portable Software ====== ====== 2018: Portable Software ======
  
Line 14: Line 13:
 Below is my very basic understanding of dependency hell.  If I go to read the Wikipedia article I just linked, I may find I just wrote complete absurdity.  (edit: I was in the ballpark) Below is my very basic understanding of dependency hell.  If I go to read the Wikipedia article I just linked, I may find I just wrote complete absurdity.  (edit: I was in the ballpark)
  
-In an ideal world, libraries would be fully backward compatible, so that a program that depends on one version of a library, would work with any newer version of that library.  But library developers don't do that, and I don't know why.  Linux wants to be ideal, and take up less hard drive space and resources (like RAM), and therefore use only one version of each library.  So sometimes you want to install two programs that both use the same library, but different versions, and this makes for dependency hell.  The portable theology, says "lets bundle the library into the program itself, so that it doesn't use the one that comes with the system".  This is contrary to the Linux ideal, but makes things much easier for the end user.+In an ideal world, libraries would be fully backward compatible, so that a program that depends on one version of a library, would work with any newer version of that library.  Linux wants to be ideal, and take up less hard drive space and resources (like RAM), and therefore use only one version of each library.  So sometimes you want to install two programs that both use the same library, but different versions, and this makes for dependency hell.  The portable theology, says "lets bundle the library into the program itself, so that it doesn't use the one that comes with the system".  This is contrary to the Linux ideal, but makes things much easier for the end user.
  
 Google Chrome does something like this, within its own program (not exactly a direct correlation with the former).  Every tab in the browser is its own process.  The downside is that Google Chrome consumes a lot more RAM compared to non-chromium-based-browsers that have all the tabs under the same process. Google Chrome does something like this, within its own program (not exactly a direct correlation with the former).  Every tab in the browser is its own process.  The downside is that Google Chrome consumes a lot more RAM compared to non-chromium-based-browsers that have all the tabs under the same process.
information-technology/2018-portable-software.txt · Last modified: 2026/01/07 00:31 by marcos

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki