alt Hacker NewsShow HN: Winpodx – run Windows apps on Linux as native windows
Comments
How does the responsiveness of the application compare between the OCI winpodx approach and a VM based winapps approach?
The OCI approach should mean that resources are not ringfenced and held separate from the host, which would be beneficial for applications run on the host. A winapps approach using a VM that is run on the host would constrain the host while the VM is running, which the VM would need to be to make sure the windows app is "always available".
Is there a noticeable performance benefit to using winpodx compared to winapps? How does the idle resource usage compare too?
Does this mean that each software you run is now the size of a windows install + sw or is it a single container that runs all your softwares ?
Interesting!
> GPU passthrough via VFIO is a manual bring-your-own setup — not yet packaged.
Can we take this to mean that GPU passthrough is planned? This would be huge especially for running Adobe/Canva software.
Might be harsh to say but not bothering to fix the spacing in the ai generated ascii diagram tells me how much i should be taking this project seriously.
[dead]
[flagged]
[dead]
WinApps doesn't use a Docker backend btw, you can use any Windows machine running anywhere - cloud, physical, container etc. All you need is the IP address of the box once it's set up.
This looks great though. +1 choosing Qt instead of Electron. -1 for Python though. Otherwise, your approach ticks most of my boxes.
One feature I'd like to see though is reverse file associations - basically associate Linux filetypes inside the Windows VM so that any file you open in a Windows app would open the file in Linux, assuming Linux has a file association for it. Say I've installed Directory Opus in the VM and I want to use it as my primary file manager in Linux, and say I double-click on a .xml file, I would like to open it in the Linux app associated with that filetype (which would be Kate in my case).