Fan of Flatpaks ...or Not?
-
Provided that flatpack has a common parent container, which is not always the case. More precisely, it almost never does. Because someone updates flatpack to new versions of the parent containers, and someone else does not.
More precisely, it almost never does.
I don't know any flatpak in my system that don't use runtime (I have around 50 flatpak apps installed), or am I misunderstanding your point
-
More precisely, it almost never does.
I don't know any flatpak in my system that don't use runtime (I have around 50 flatpak apps installed), or am I misunderstanding your point
wrote on last edited by [email protected]runtime have versions too. If one runtime version use only one flatpack than exactly same as just static linking binary. Flatpack have just docker layeredfs and firejail in base.
id: org.gnome.Dictionary runtime: org.gnome.Platform runtime-version: '45' <- here sdk: org.gnome.Sdk command: gnome-dictionary -
This post did not contain any content.
never tried flatpak, snaps were so bad as to never consider non-native installs or just use docker instances when I need to run something weird. so dunno.
whats the use case for a flatpak exactly? maybe im not the target audience???
-
This post did not contain any content.
./configure
make
make install -
I've been working on Linux for 15 years now and I perfectly remember the origin of many concepts. If you look at it through time, what would it be like:
- We can build applications with external dependencies or a single binary, what should we choose?
- The community is abandoning a single binary due to the increased weight of applications and memory consumption and libraries problems
- Dependency hell is coming
... - Snap, flatpack, appimage and other strange solutions are inventing something, which are essentially a single binary, but with an overlay (if the developer has hands from the right place, which is often not the case)
- Someone on lemmy says that he literally doesn't care if the application is built in a single binary, consumes extra memory and have libraries problems. Just close all permissions for that application...
Well, all I can say about this is just assemble a single binary for all applications, stop doing nonsense with a flatpack/snap/etc.
UPD: or if you really want to break all the conventions, just use nixos. You don't need snap/flatpack/etc.
Old guy here too, used un*x before linux existed in the 90s. I still use a Debian based distro (MX) without systemd and no snap/flatpak/whatever. Just build/compile or install .deb and dependencies. Lastly unfortunately I had to install a flatpak to test "deskflow", the first time I installed one, I feel dirty now
-
Flatpaks suck
Ubuntu has turned to dogshit
i agree ubuntu is corpo drivel now but flatpaks are actually quite useful for some applications.
the sandboxing is nice to not have to setup manually for every little thing, and i say that as someone who avoids flatpaks generally.
sometimes you just wanna get things up and running, not everything needs to be a unix circlejerk.
-
runtime have versions too. If one runtime version use only one flatpack than exactly same as just static linking binary. Flatpack have just docker layeredfs and firejail in base.
id: org.gnome.Dictionary runtime: org.gnome.Platform runtime-version: '45' <- here sdk: org.gnome.Sdk command: gnome-dictionaryI see problem in that only in unmaintained apps (like org.gnome.Dictionary), I have only GNOME 47 & 48 for example and both of them still updating
-
I see problem in that only in unmaintained apps (like org.gnome.Dictionary), I have only GNOME 47 & 48 for example and both of them still updating
In the initial stage of shared library support, everything was exactly the same. Let's look at it in 5 years... When some soft will archived and die, some stop maintaining, some new crated and brakes old dependencies...
-
never tried flatpak, snaps were so bad as to never consider non-native installs or just use docker instances when I need to run something weird. so dunno.
whats the use case for a flatpak exactly? maybe im not the target audience???
Flatpaks mean you don't have to compile everything from scratch and solve dependency conflicts if you want a newer version of a program than what's available in your distro's repo, of if it's something that doesn't have a native version at all.
-
I have used rpms, AppImages, Flatpaks, and source. I have even used a snap or two when I had no other choice.
If you can't work with them all, can you even say you Linux Bro?
Bro, TRUTH. I have preferences but when you gotta get something done, it doesn't matter how the app comes bundled. I'd run .exe's through Wine if I needed to.
-
This post did not contain any content.
Honestly, i'm not entirely sure what Flatpaks are all about. Not sure I could explain them. But I use them. I've used apt. I've even used Pacman and Yay in Manjaro for a few years. Now, I also Flatpak (no longer on Manjaro, though. I no longer boot to a blank screen every 6 months or so! Very nice!)
-
This post did not contain any content.
Flatpaks are great for situations where installing software is unnecessary complex or complicated.
I have Steam installed for some games, and since this is a 32 bits application it would install a metric shit-don of 32 bit dependencies I do not use for anything else except Steam, so I use the Flatpak version.
Or Kdenlive for video editing. Kdenlive is the only KDE software I use but when installing it, it feels like due to dependencies I also get pretty much all of the KDE desktop’s applications I do not need nor use nor want on my machine. So Flatpak it is.
And then there is software like OBS, which is known for being borderline unusable when not using the only officially supported way to use it on Linux outside of Ubuntu – which is Flatpak.
-
Flatpaks are great for situations where installing software is unnecessary complex or complicated.
I have Steam installed for some games, and since this is a 32 bits application it would install a metric shit-don of 32 bit dependencies I do not use for anything else except Steam, so I use the Flatpak version.
Or Kdenlive for video editing. Kdenlive is the only KDE software I use but when installing it, it feels like due to dependencies I also get pretty much all of the KDE desktop’s applications I do not need nor use nor want on my machine. So Flatpak it is.
And then there is software like OBS, which is known for being borderline unusable when not using the only officially supported way to use it on Linux outside of Ubuntu – which is Flatpak.
works perfectly with my Arch Linux
-
Flatpaks suck
Ubuntu has turned to dogshit
Ubuntu is using Snaps though...
-
This post did not contain any content.
It just doesnt work half the time. I avoid them as much as possible.
-
Honestly, i'm not entirely sure what Flatpaks are all about. Not sure I could explain them. But I use them. I've used apt. I've even used Pacman and Yay in Manjaro for a few years. Now, I also Flatpak (no longer on Manjaro, though. I no longer boot to a blank screen every 6 months or so! Very nice!)
Flatpaks are basically containers, allowing applications to maintain their own dependencies separate from your system. It's similar to a Windows program shipping with its own precompiled DLLs, helping prevent dependenct conflicts when you go to update something you installed with pacman or yay.
-
This post did not contain any content.wrote on last edited by [email protected]
I spent my time fighting AppImages until Canonical started to force Snap on me. I hated Snap so bad it forced me to switch distros. Now I appreciate Flatpak as a result and I don't find AppImages all that bad, either. Also, I haven't found myself in dependency-hell nor have I crashed my distro from unofficial Repos in well over a decade.
-It's a long way of saying It works for me and it's not Snap.
-
It is mostly trial and error. I use it mostly to set envvars.
As an example, I add the ~/.themes folder and the GTK_THEME to allow some apps to get the themes I downloaded.
Oh, so flatpaks cannot automatically get system themes?
If it is trial and error, is it really useful for a normal user?
-
Flatpaks are good, especially compared to snap.
The future is atomic OS's like silverblue, which will make heavy use of things like flatpak.
Snap is not all bad if you're on a Ubuntu based distro, I just don't like the way it's pushed and that it comes from Ubuntu mostly. Startup time is a major issue for me also, but all in all it works.
I'm still sitting on the fence, heavily prefer flatpak but when Ubuntu is going to package nvidia drivers in a snap it's a thing I'm up for trying.
My understanding is that if I'm on Ubuntu and the snap uses the same underlying Ubuntu version as my distro it should be fast but I haven't seen it.
-
Wait how do you install flatpaks? I add the remote (if necessary) and then install it from there. That is nothing like I have ever seen on Windows (though apparently there are package managers).
I think he's referencing the flathub install button where you can just hit install.
