this post was submitted on 05 Apr 2026
16 points (76.7% liked)

Hacker News

4753 readers
427 users here now

Posts from the RSS Feed of HackerNews.

The feed sometimes contains ads and posts that have been removed by the mod team at HN.

Source of the RSS Bot

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] SamueruSama@programming.dev 1 points 2 weeks ago

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