>>109477936
The main problem I have with this is lack of backwards compatible ABIs
The moment you want to make an application portable is the moment where you need to statically link every library, including the regressions, vulnerabilities, and so on, the inability to update such application is one problem, and then there's another: size.
SSDs and memory aren't cheap anymore and wear out pretty quickly.
Having to incorporate a gazillion libraries into one executable results in quite some size compared to distribution managed, dynamically linked applications.
It's the painful problem with app images, flat packs, otherwise portable applications.

>>109477936
Why?

>>109477936
snap and flatpak are package managers for portable apps
it all goes in circles

>just do a google search and jump through multiple hoops, like avoiding fake download buttons and waiting timers to download every program
no thanks

Package managers are nice but there is one case where I feel like they are worse than using an installer: software becoming worse. There's a bunch of stuff that already has all the functionality you need but they keep making superficial updates that change the software for the worse, like maybe the UI becomes such that I prefer the old version. Now, you can just freeze the package in your package manager to make sure it doesn't update but if you are setting up a new system and you want that old version it might be a huge headache to get it and you might need to resort to finding old source and building from it. On Windows I could just download an installer for any damn version I pleased.

>>109478153
in a decent package manager you can just roll back to the version you prefer, if other packages that depend on that one will keep working well is another matter

>>109478209
I don't think most repos keep a ton of outdated versions or anything. Sure you can roll back to previous version if you are not happy with an update but you can't just be like okay give me qbittorrent from 5 years ago. Unless some distros allow this and I'm not aware.

>>109478054
A single game nowadays can take more space than my whole system partition, I would trade some space overhead over the flexibility of putting my programs where I want to put them.
>>109478054
moving things away from your system partition to separate /home means you can reinstall your system after you fuck up something in the config files, or you want to change your distro. If everything lives on your system partition, you must fix everything manually with chroot.
>>109478113
*supply chain attacks your trusted software vendor*

>>109478357
What games are you installing from a package manager? Super Tux Kart?

>pic
and this ones going into the collection. thanks for sharing such a wonderful image.

>>109478413
I'm just saying that saying that 100MB of space saved by dynamic linking doesn't matter in the grand scheme of things

>>109478357
>moving things away from your system partition to separate /home means you can reinstall your system after you fuck up something in the config files
In current year I prefer to have one btrfs volume divided into / and /home subvolumes with automatic snapshots of / so if anything breaks I can just restore a snapshot from when it was not broken to / and /home will not be rolled back. Very comfy but I know some people still have allergy to btrfs.

>>109478357
you don't need btrfs. i use my distro's package manager to provide build tools, compilers and libraries. then every program I use is compiled and installed locally.

I do have separate /home and /, so if I fuck up I can always reinstall / (takes 10-20 minutes), then everything is still working because I never rollback glibc version or whatever.

>>109477936
What problems winshitters have with package managers? They're already solved, nobody have problems with package formats anymore

>>109478469
>but I know some people still have allergy to btrfs
Rightfully so. I remember when I first tried btrfs when I wanted to try OpenSUSE because it was the default. It got corrupted within the first day of use. It musth have been a decade by now but I still avoid it.

>>109478413
Steam is a package manager

>>109477936
The actual problem is that tree shaking algorithms in most languages are really shitty. If it weren't for that I think just making everything static would be ideal. With maxed out tree shaking, there should be very little space and memory overhead (the latter only on OSs that don't hash and COW images in memory).

>>109479854
You can manage where Steam installs the games so it's irrelevant. Also use GOG.

>>109477936
No
>>109478041
Musl
>>109478054
He used windows one time
>>109478068
Terrible ones
>>109478153
Don't install bad software
>>109478209
This too

>>109478357
Supply chain attack my asshole
>>109478413
All my favorites, yo
Check it:
Xonotic. Doom. Openttd. Openrct2.
>>109478443
Yeah that's why you use windows you don't care about the megarbytes
>>109480093
GOG. Itch. Humble. Zoom. Anything except steam, the worst one that requires it's own spyware bloatware DRM client and login with internet connection so I can play the same game I did a decade ago.

>>109478041
>The main problem I have with this is lack of backwards compatible ABIs
>The moment you want to make an application portable is the moment where you need to statically link every library, including the regressions, vulnerabilities, and so on, the inability to update such application is one problem
Oh fuck off you disingenuous reddit parroting nufreetard.

Heres what actually happened:
>NS and CF ecosystem was lagging behind Win32
>POSIX was dying glued together cope from 3,000 different vendors shipping BSD forks
>POSIX tards were coping as their chosen multiseat OS was dying
>Apple fags started crying about "muh DLL hell"
>POSIX tards joined
>After a while, they started crying about "muh static linking" despite (1) having a worse link time environment and (2) their dumpsterfire of an OS being nothing more than a toy c program meant to be nothing more as a little jmp 0xNextProcess thing with some static HAL layer over the BIOS
>To deal with the aforementioned toy operating systems issues, package jannies came around to larp as software developers for power, control, and globalist buckerinos
>...these pathetic fags needed to gaslight the world into believing they offer something of value.
>Fast forward to current era:
>...still a toy 80s C operating system
>...package jannies still larp as value adders
>...package jannies still larp as "the eyes of FOSS" making sure everything is secure
>...package jannies still seethe when anybody tries to go around them and their power structures
>now redditors debate "static" vs "dynamic" linking as if there's a god damn difference philosophy or major limitations between operating system vendors
(real issue: package jannies and troonix vendors fucking suck at shipping a workable operating system runtime)
>now redditors debate linking as this great philosophical matter when all of their issues stem from freetards being incapable of writing and shipping software more complicated than an assembly-based /bin/cat
(1/2)

>>109483941
>>109478041
>The main problem I have with this is lack of backwards compatible ABIs
>The moment you want to make an application portable is the moment where you need to statically link every library, including the * regressions, vulnerabilities, and so on, the inability to update such application is one problem *
Guess what cocksucker? You aren't patching old software to fix security issues. That was always a system jannie larp.

If you cared about updating your software, you'd just wget http://ivansnginxfork.com/linux.bin, chmod +x, and just run the damn thing. Instead you spin these cope stories about needing to fix totally real security issues your shitty file mode permission system cant catch, for what? To justify the existence of package jannies? To break your toy 80s operating system with busted packages every weekend because *everything* has to depend on each other? We all know you aren't patching shit without ABI breakages, version conflicts, and everything from your init deamon to your fucking python based firewall crashing down.... so why even larp that you even care about patching? You could trivially patch software regardless of linkage style, but you refuse to.

"but muh statically linked regressions" what the fuck does that even mean? how do you statically link future events that havent even happened yet?
(2/2)

>>109483941
>dumpsterfire of an OS being nothing more than a toy c program meant to be nothing more as a little jmp with some static HAL layer over the BIOS
Correction: [despite their] dumpsterfire of an OS being nothing more than a toy c program of a little jmp 0xNextProcess thing complete with some static HAL layer over the BIOS *

Bad edit. Still babbly but you should get my point.