Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
As far as I’m concerned Flatpak has won the “universal Linux package manager” war.
Snap is a non-starter because of its proprietary back end, appimage has no distribution or automation built in. Flatpak has its faults (why does it put things in /var of all places?) but it’s the best I’ve seen.
I’d like to add: I think it’s won not by being the best, but being the least worst. I would like to invite whoever came up with that com.flatpak.FlatPak bullshit to consider a career more suited to their skill set than computer programming, such as vagrancy.
As far as I’m concerned Flatpak has won the “universal Linux package manager” war.
Snap is a non-starter because of its proprietary back end, appimage has no distribution or automation built in. Flatpak has its faults (why does it put things in /var of all places?) but it’s the best I’ve seen.
I’d like to add: I think it’s won not by being the best, but being the least worst. I would like to invite whoever came up with that com.flatpak.FlatPak bullshit to consider a career more suited to their skill set than computer programming, such as vagrancy.
I thought the com.flatpak.Appname came from Android, so I guess google is to blame?
/var is really annoying, especially when partitioning, previously I could just have a /var partition, but now I need to do /var/log specifically
I mean doesn’t that come from Java naming conventions? Which then makes sense that it continued on Android… but Why did it end up on FlatPack!?
I will speculate to say that maybe someone looked at the java/android way and thought let’s just copy that.
It’s the most plausible answer I can think of, without doing any research whatsoever
It’s a nice way to get around naming collisions.
Well yeah that’s true
Holy shit the end (skull emoji)