932
you are viewing a single comment's thread
view the rest of the comments
[-] uis@lemmy.world 2 points 1 year ago

shared dependency is not scalable

Explain yourself.

a loud minority

Kernel develipers, libraries developers, compiler developers, distro maintainers, mirrors hosters, anyone whose system runs not on few terabytes disk and gigabit internet.

I heard some geniuses put entire graphical drivers into snap/flatpak/appimages.

[-] baseless_discourse@mander.xyz -1 points 1 year ago* (last edited 1 year ago)

Correct me if I am wrong.

Different app depends on different version of the underlying softwares. In the old days distro packages apps, however it would cause dependency hell.

Hence with the development in containers, universal packaging format prevails, where each app is packaged with all of its dependencies. so that the system dont need to maintain the dependency of every single app people want to use.

[-] uis@lemmy.world 1 points 1 year ago

Different app depends on different version of the underlying softwares.

On different ranges of versions. Usually something like "1.2 or newer". With few exceptions that break ABI every year(looking at you, Boost) or 11 times a month(it is rust, who would have guessed). If everything was as hard as you described, then there is no way for me to play UT2004 back from, you guessed it, 2004. But I did, and all I needed just to install few 32-bit version of libraries and run it with OSS(very old audio api) emulation.

however it would cause dependency hell.

No, task of package manager is to solve dependency hell

universal packaging format

We had 2 universal packaging formats, now we have 5 universal packaging formats and two container types.

where each app is packaged with all of its dependencies.

Which in case of UT2004 means packaged with all exploits back from 2004.

this post was submitted on 06 Oct 2023
932 points (96.0% liked)

linuxmemes

21280 readers
1111 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 2 years ago
    MODERATORS