3 ms·

I think this article is not providing adequate alternatives. Most programs link against quite a bit more than libstdc++ and you clearly can't expect users to i

by dxuh 5y ago

I think this article is not providing adequate alternatives. Most programs link against quite a bit more than libstdc++ and you clearly can't expect users to install a bunch of packages to get their program running. Those extra libraries usually take up most of the space in a package. If you include all the shared libraries you need, apart from the system libraries in your distribution, you pretty much have an AppImage already, just as a tarball instead of a squashfs image. I think GOGs path is not horrible, but it is much less effective at making Linux a viable alternative as a gaming platform. They literally only support Ubuntu 16.04 and 18.04. It also struck me as odd, that the author was complaining about the complexity introduced by Proton. What is Valve supposed to do?

southerntofu 5y ago
> you pretty much have an AppImage already That's not wrong, but AppImage is focused on the UX of the application as single file, which you can move/copy around and can be integrated with the desktop launcher, which i personally don't know of standard solutions for with a classic tarball. For example, Tor Browser is a classic tarball and works great, but the .desktop generation relies on some hacks rather than a properly-defined mechanism. > the author was complaining about the complexity introduced by Proton That's not what i understood from the article. I mean wine/proton makes sense on its own to run Windows apps, i think the author was criticizing that their specific approach relies on steam-specific runtimes instead of using system libraries.