<story><title>Pengwin – A Linux Distro Optimized for WSL Based on Debian</title><url>https://github.com/WhitewaterFoundry/Pengwin</url></story><parent_chain><item><author>ncmncm</author><text>This is fundamentally the wrong direction to go.&lt;p&gt;The clue is that MSWin running in a VM on Linux is faster than on hardware. The way forward is to boot Linux, or even something else, to manage hardware, memory, and filesystems, and cut down MSWin to run in a container on it. That way MSWin relies on the underlying OS to do things MSWin has proven to be just not very good at. MSWin runs programs written for it, reliably the same as non-hosted MSW, but is not subject to randomizing effects of manufacturers&amp;#x27; drivers and MS&amp;#x27;s historically poor buffer and process management.&lt;p&gt;If you want MSWin to manage the screen, it can provide a way for an underlying OS program to work in a window it provides, and connect UI and clipboard events back to it. But MSWin is not really so great at display management, either, so it might be better for the underlying OS to manage that, too, as is done with VMs on X today.</text></item></parent_chain><comment><author>losvedir</author><text>&amp;gt; &lt;i&gt;The clue is that MSWin running in a VM on Linux is faster than on hardware.&lt;/i&gt;&lt;p&gt;I&amp;#x27;ll join the fray in expressing skepticism here. Source?&lt;p&gt;Anyway, I think this WSL distro is pretty cool. I&amp;#x27;ve set up WSL on my Windows computer for kicks and while it was neat I never quite got it to work for the rust development and environment I wanted. I ended up just doing it in Windows.&lt;p&gt;But if this sets up rust and VS Code (the editor I wanted to use) painlessly, then I&amp;#x27;ll have to give it another shot.</text></comment>
<story><title>Pengwin – A Linux Distro Optimized for WSL Based on Debian</title><url>https://github.com/WhitewaterFoundry/Pengwin</url></story><parent_chain><item><author>ncmncm</author><text>This is fundamentally the wrong direction to go.&lt;p&gt;The clue is that MSWin running in a VM on Linux is faster than on hardware. The way forward is to boot Linux, or even something else, to manage hardware, memory, and filesystems, and cut down MSWin to run in a container on it. That way MSWin relies on the underlying OS to do things MSWin has proven to be just not very good at. MSWin runs programs written for it, reliably the same as non-hosted MSW, but is not subject to randomizing effects of manufacturers&amp;#x27; drivers and MS&amp;#x27;s historically poor buffer and process management.&lt;p&gt;If you want MSWin to manage the screen, it can provide a way for an underlying OS program to work in a window it provides, and connect UI and clipboard events back to it. But MSWin is not really so great at display management, either, so it might be better for the underlying OS to manage that, too, as is done with VMs on X today.</text></item></parent_chain><comment><author>andyonthewings</author><text>&amp;gt; MSWin running in a VM on Linux is faster than on hardware.&lt;p&gt;That&amp;#x27;s funny. I didn&amp;#x27;t know that. Any data source you can share with me?</text></comment>