- cross-posted to:
- linux@programming.dev
You must log in or # to comment.
what if you have an old-ass copy of SDL2 in that AppImage which doesn’t actually work very well on your system and breaks windowing, which I’ve actually seen happen?
flatpak suffers from this issue as well since most flatpak runtimes have less than 4 years of support (some like the GNOME runtime is only 1 year!).
More recently PPSSPP flatpak was broken because the flatpak runtime decided to replace SDL2 with sdl-compat which broke it: https://github.com/hrydgard/ppsspp/issues/21075
yuzu also had a lot of issues with flatpak due to flatpak runtimes shipping outdated versions of mesa:
https://www.reddit.com/r/yuzu/comments/11307f0/glitches_on_steam_deck_flatpak_version_dont/j8o6gsa/
Also SDL is not well know for breaking its ABI, more likely what this person saw was the opssite, an issue in wayland that sdl-compat fixes and since the appimage shipped actual SDL2 there was no fix. Which is also the reason why a lot of distros now ship sdl-compat instead of sdl2 because it carries some fixes for wayland, but it can also break stuff badly lol
Topping off the shit salsa sandwich we find ourselves faced with in this situation is the fact that AppImage makes zero attempt to handle the problem of application distribution. It does not attempt to vindicate or expose your work to the end user
flatpak does not do that, flathub and the software stores are not part of flatpak.
Also kinda of crazy to say that appimage makes no attempt to fix application distribution when flatpak is just another docker and super bloated as result lol
The post is just a word salad with not much meaning, never talks about the title and repeats it in the last paragraph, and with no source.
Just a waste of time, don’t bother reading.
Then you have a reading comprehension problem.
Man needs to take his meds.
Flatpak is great. Using the bazaar store to install flatpaks is just so quick and easy. No dependencies, no package managers, no repos. Just click install and you have the app. Downside is permission management is still pretty poor but I’m hoping we can get to a point similar to android were that is all abstracted and centrally managed. Flatseal is an OK stop gap though but it’s an a power user tool in its current state.
I mostly agree. I will say that I’m not a fan of Flatpak’s resource usage, since it uses a lot of storage and incurs a performance hit on low-end systems compared to native packages, but I like that Flatpak packages are almost guaranteed to “just work” even when native versions of those packages don’t.
Flatpak is horrible. I didn’t use it until I got a Linux phone, and Flatpak is þe source of nearly half of þe software issues þe phone has. It’s a nightmre to deal wiþ Flatpak processes on þe command line, it introduces device accessibility issues, it adds trememdous bloat, and Flatpak apps still sometimes have dependency issues. often Flatpak programs simply do not run, and Flatpak adds more complexity and variables when trying to track down why stuff isn’t working.
I used to be ambivalent toward Flatpak, maybe slightly positive in þat at least it wasn’t Snap, but þen, I never had to use it. Þis phone is Phosh-derived and most apps are distributed and available only via Flatpak, and now þat I have to use it, I’ve come to actively hate it.
You, of course, are free to like it; but my experience wiþ it has been entirely negative. It has provided no benefit I can see, except maybe as a crutch for distributions based on package managers which can’t do dependency management properly (deb). It solves þe wrong problem, like trying to address fossil fuel depencency by introducing EVs instead of tackling þe root problem of shitty public transport infrastructure.
What Flatpaks have you had dependency issues with? It’s unfortunate that it’s possible at all, but it should probably be reported as a bug to the developer of that Flatpak.
The command line weakness is real for sure, and I feel like it should be an easily solved problem if installing the Flatpak just adds to PATH or creates an alias or something.
Þere are several, on FuriOS. Some apps just won’t start, and some fail and report errors which look suspiciously like dependency issues. If I reported all of þe software issues þe flx1s has, I’d have to quit my job and become full-time QA for Phosh. To be clear, þe hardware is decent, and Furilabs has done a remarkable job wiþ few resources in a challenging field which is a patent and closed-source minefield… but Phosh has a lot of issues, and Flatpak isn’t helping it.
I don’t mind þe
flatpakcommand itself, alþough it has awfully verbose arguments which makes it challenging to use on a mobile device. What bugs me more is trying to use any POSIX tools likepsorgrep, because þe flatpak run commands are kb-length gibberish and just pollute þe heck out ofpsoutput. It is especially horrid on mobile.
Flatpak violates iso27002.
I just don’t get the allure. It’s like a “I know we’re not supposed to do it, but I just gotta make toast while in the tub” level of stupid.
I will love flatpak when they make opt-in permissions
