Our great sponsors
-
docker-wine
Docker image that includes Wine and Winetricks for running Windows applications on Linux and macOS
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
AppImageKit
Package desktop applications as AppImages that run on common Linux-based operating systems, such as RHEL, CentOS, openSUSE, SLED, Ubuntu, Fedora, debian and derivatives. Join #AppImage on irc.libera.chat
-
AppImageLauncher
Helper application for Linux distributions serving as a kind of "entry point" for running and integrating AppImages
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Statically compiled Wine library through Docker Sounds like this wouldn't introduce the burden of installing multilib dependencies onto the host. Although the project itself is still in an experimental phase and honestly it seems like this approach asks for more trouble than it's worth even though it's extremely neat: https://github.com/MIvanchev/static-wine32
Docker container This alternative would eat more resources than necessary as an additional OS would be running in the background. I've also noticed that displaying the application in X11/Wayland this way seems to introduce an overhead if no GPU is shared with the container (which is negligible with the proper configuration): https://github.com/scottyhardy/docker-wine
AppImage This seems like a convenient way of keeping Wine isolated from rest of the system. However, the documentation is still in research phase for this: https://github.com/AppImage/AppImageKit/wiki/Bundling-Windows-applications https://github.com/probonopd/go-appimage https://github.com/TheAssassin/AppImageLauncher https://github.com/sudo-give-me-coffee/wine32-deploy
AppImage This seems like a convenient way of keeping Wine isolated from rest of the system. However, the documentation is still in research phase for this: https://github.com/AppImage/AppImageKit/wiki/Bundling-Windows-applications https://github.com/probonopd/go-appimage https://github.com/TheAssassin/AppImageLauncher https://github.com/sudo-give-me-coffee/wine32-deploy
AppImage This seems like a convenient way of keeping Wine isolated from rest of the system. However, the documentation is still in research phase for this: https://github.com/AppImage/AppImageKit/wiki/Bundling-Windows-applications https://github.com/probonopd/go-appimage https://github.com/TheAssassin/AppImageLauncher https://github.com/sudo-give-me-coffee/wine32-deploy
AppImage This seems like a convenient way of keeping Wine isolated from rest of the system. However, the documentation is still in research phase for this: https://github.com/AppImage/AppImageKit/wiki/Bundling-Windows-applications https://github.com/probonopd/go-appimage https://github.com/TheAssassin/AppImageLauncher https://github.com/sudo-give-me-coffee/wine32-deploy
Conty This looks interesting as most of the things are ready to go. Not sure if there's any bottlenecks with this approach: https://github.com/Kron4ek/Conty