winapps

What percentage of MS Office user can, in your estimation, complete the steps as described in this readme? https://github.com/winapps-org/winapps

https://github.com/winapps-org/winapps fusion360 is supported.

I haven't tried it but I've seen this project promoted in some tweets and maybe even here: https://github.com/winapps-org/winapps

I've linked it multiple times on HN already but winapps (https://github.com/winapps-org/winapps) can be a game-changer for people relying on some Windows-only software. It sets up a Windows machine in Docker where you can install your apps, then you'll get .desktop applications that starts the program in the VM and use RDP to only show the app window – it feels nearly native. I've even bought an Office 2024 license to improve some VBA Excel macros for a client.

I am in a similar boat; my media editing machine ruined windows 10 so that I can use Lightroom. But I would dearly love to ditch windows so I'm currently looking to try out running Lightroom under Winapps to see if it is usable. There's no way of passing the GPU through without something like SR-IOV so I'll have to see how it goes. https://github.com/winapps-org/winapps

Winapps is pretty good to run the Microsoft office suite. https://github.com/winapps-org/winapps A office specific winapps fork : https://github.com/eylenburg/linoffice/

Note that it currently only works with xfreerdp¹, so that means you share the X11 socket with this program. Although freerdp is also available for Wayland, the single app mode (aka RemoteApp aka RAILS) reportedly has not been implemented yet on the SDL port. 1. https://github.com/winapps-org/winapps/issues/779

The container is a Linux container running a virtual machine inside. WinApps needs a Windows RDP server to work. Most of the functionality doesn't care where that Windows RDP server is actually running as long as its FreeRDP client can connect to it. The container or libvirt VM options are just ways to accomplish that via virtualization. I imagine the container part makes it easier to automate QEMU virtualization using bash scripting without worrying about distribution specific differences in the environment. These kinds of scripts become fairly ossified to their environment. Making them run consistently on different Linux distributions is its own adventure unrelated to installing and running Windows, so the containerization eliminates the need for a lot more bash scripting to account for those differences. The container's bash scripts do

Once the masses discover that KDE is just as user friendly as Windows these days, ... ... and that it is relatively easy to run (most) Windows apps they love through Bottles (https://usebottles.com/), and/or WinApps (https://github.com/winapps-org/winapps)... ... oof

WinApps is the project to watch (https://github.com/Fmstrat/winapps), although they're still working on Wayland support (https://github.com/winapps-org/winapps/issues/779#issuecomme...). It can get by through xwayland for the time being, it seems.

Is it WinApps[0] with some fancy GUI or something? [0] https://github.com/winapps-org/winapps

It's a full VM running via Docker. The Windows apps are presented via RDP's RemoteApps protocol via FreeRDP. There's also WinApps, which is the same thing but without the docker container, and it supports a remote VM as well: https://github.com/winapps-org/winapps

You can use WinApps for that instead - supports both local and remote VMs. https://github.com/winapps-org/winapps