Email or username:

Password:

Forgot your password?
TSource Engine Query's posts Post Back to profile
Top-level
[:babaKatt:] Cacofren :ironFront:​​:enbyCrossbow:​​:sparkles2:
3 comments
TSource Engine Query
@katnjiapus no.

There is so much wrong about it. I do not recommend it, if it's possible literally any other solution will be better than AppImage.
19 April at 11:49 | Open on suya.place
[:babaKatt:] Cacofren :ironFront:​​:enbyCrossbow:​​:sparkles2:

@a1ba from a user perspective, AppImage is one of my favs. I don't have to worry about the image being unusable after several updates.

19 April at 11:51 | Open on twoot.site
TSource Engine Query
@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.
@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.
19 April at 12:05 | Open on suya.place
Go Up