Gregory's Server
@katnjiapus the thing is, it easily can be unusable.
You just execute an SFX archive, and god knows what's inside. It's basically up to developer to ensure that their program won't break on most Linux distros, and also make it future-proof.
Let's say you run a Qt application. Qt has platform plugin system, there is one for X11, there is another for Wayland. What if developer who personally uses one of them didn't put a plugin for another? Can you fix it? Until you find a binary for the exact same Qt version, no.
Or let's say it's a game. It knows about both X11 and Wayland and should work everywhere, right? WRONG. If you use Mesa drivers, the dependency tree might be complex enough to be incompatible with included in AppImage dependencies. It was a problem for Steam Runtime until sniper, which addressed this problem.
Even Steam moved on, but AppImage didn't because AppImage is just a glorified SFX archive.
You just execute an SFX archive, and god knows what's inside. It's basically up to developer to ensure that their program won't break on most Linux distros, and also make it future-proof.
Let's say you run a Qt application. Qt has platform plugin system, there is one for X11, there is another for Wayland. What if developer who personally uses one of them didn't put a plugin for another? Can you fix it? Until you find a binary for the exact same Qt version, no.
Or let's say it's a game. It knows about both X11 and Wayland and should work everywhere, right? WRONG. If you use Mesa drivers, the dependency tree might be complex enough to be incompatible with included in AppImage dependencies. It was a problem for Steam Runtime until sniper, which addressed this problem.
Even Steam moved on, but AppImage didn't because AppImage is just a glorified SFX archive.