Well it does technically, the issue we’re talking about is how it’s packaged, one you extract the package the software will work just the same (assuming there aren’t any version mismatches between kernel modules). DEBs (Debian based distros) and RPMs (RedHat based distros) are the two biggest package formats, the next common format is a tar ball.
Add to this, this gives birth to more modern packaging format like flatpak, appimage, and snap, that works across all distro with proper permission control.
Now for most graphical apps, you just search on the app store and click install, like a iphone user.
There are different aspect to the same product. IPhone is lockeddown and aniconsumer, but it doesn’t mean every aspect of it is not worth taking a lesson from.
In order for linux to have mass apeal, it will need to be simple by default, and that is where the app store model shines, you just search and click install, everyone can figure that out.
But that doesn’t imply linux has to be lockdown and anticonsumer like iphone. If you want to compile your own kernel, you should have freedom to do so.
Except now you dont need to worry about outdated software even on a super stable base. You get proper permission control and a mispackaged app cannot break the entire system.
I think you might be talking about two group of Linux user. I think majority of the user realized that shared dependency is not scalable in the recent couple years, yet there are still a loud minority that oppose dupilicated dependencies that exists in these universal formats.
Finally, I think the three universal package formats provide better sandboxing support than msi. But appx in windows are very much inline with these packaging formats.
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.
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.
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.
Well it does technically, the issue we’re talking about is how it’s packaged, one you extract the package the software will work just the same (assuming there aren’t any version mismatches between kernel modules). DEBs (Debian based distros) and RPMs (RedHat based distros) are the two biggest package formats, the next common format is a tar ball.
Add to this, this gives birth to more modern packaging format like flatpak, appimage, and snap, that works across all distro with proper permission control.
Now for most graphical apps, you just search on the app store and click install, like a iphone user.
Don’t mention the S-word here, some people might come out of their basement to tell you how it’s the worst thing since proprietary software.
I DON’T WANT THIS
https://www.youtube.com/shorts/59dQ-5sjDLc
Iphone is most locked-down anti-consumer pile of garbage and this is how you defend it?
There are different aspect to the same product. IPhone is lockeddown and aniconsumer, but it doesn’t mean every aspect of it is not worth taking a lesson from.
In order for linux to have mass apeal, it will need to be simple by default, and that is where the app store model shines, you just search and click install, everyone can figure that out.
But that doesn’t imply linux has to be lockdown and anticonsumer like iphone. If you want to compile your own kernel, you should have freedom to do so.
This is how linux works for last 30 years…
Except now you dont need to worry about outdated software even on a super stable base. You get proper permission control and a mispackaged app cannot break the entire system.
How did this come up in discussion?
Anyway. Mispackaged app may also include broken permission control.
Here is an alternative Piped link(s):
https://www.piped.video/shorts/59dQ-5sjDLc
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.
deleted by creator
I think you might be talking about two group of Linux user. I think majority of the user realized that shared dependency is not scalable in the recent couple years, yet there are still a loud minority that oppose dupilicated dependencies that exists in these universal formats.
Finally, I think the three universal package formats provide better sandboxing support than msi. But appx in windows are very much inline with these packaging formats.
Explain yourself.
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.
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.
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.
No, task of package manager is to solve dependency hell
We had 2 universal packaging formats, now we have 5 universal packaging formats and two container types.
Which in case of UT2004 means packaged with all exploits back from 2004.
deleted by creator