Every reply by OP sounds like AI.
Yes, looking at their profile it does look that way for all their contributions on HN. Ctrl+F "real" and Ctrl+F "genuine" as one quick indicator--AI absolutely loves these adjectives and their forms right now.
Show HN: Winpodx – run Windows apps on Linux as native windows
31–40 of 54 posts
Re: Show HN: Winpodx – run Windows apps on Linux as native windows
#32Can we take this to mean that GPU passthrough is planned? This would be huge especially for running Adobe/Canva software.
Re: Show HN: Winpodx – run Windows apps on Linux as native windows
#33Re: Show HN: Winpodx – run Windows apps on Linux as native windows
#34> 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.
Re: Show HN: Winpodx – run Windows apps on Linux as native windows
#35Re: Show HN: Winpodx – run Windows apps on Linux as native windows
#36Re: Show HN: Winpodx – run Windows apps on Linux as native windows
#37[flagged]
Re: Show HN: Winpodx – run Windows apps on Linux as native windows
#38Does 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 ?
Re: Show HN: Winpodx – run Windows apps on Linux as native windows
#39So, Linux subsystem for Windows?
Re: Show HN: Winpodx – run Windows apps on Linux as native windows
#40The 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?