I already asked this in the past, and want to ask again. Is Microsoft a corporation of goodness now?
Embrace Extend Extinguish
Windows Subsystem for Linux GUI
131–140 of 473 posts
Re: Windows Subsystem for Linux GUI
#132Will I be able to use i3?
Re: Windows Subsystem for Linux GUI
#133I wonder what Linux exclusive software they are hoping to support. Everything I use in my Ubuntu daily driver has a Windows build or corollary app. I get how ‘you never have to leave Windows’ is a nice thing for their business, but I don’t see this being a reason I would stop dual-booting. The only reason I run windows in the first place is for a few apps, mostly games. Otherwise I really enjoy the bloat-free, ad-fre…
Re: Windows Subsystem for Linux GUI
#134Earlier quoted context omitted.
Accessing the Windows filesystem from WSL and vice versa is extremely slow, so running for example your IDE in WSL and having your code etc. stored in WSL is useful. I think that is one of the big usecases. It's already kinda supported in vscode, where it runs a vscode server in WSL and Windows just runs the frontend. It's useful for me when developing dotnet intended for Linux as I can store the code in WSL and be a…
Are you talking about WSL1 or WSL? Wsl2 is much much faster due to having a virtualized real linux kernel running
https://docs.microsoft.com/en-us/windows/wsl/compare-version...
> As you can tell from the comparison table above, the WSL 2 architecture outperforms WSL 1 in several ways, with the exception of performance across OS file systems.
Re: Windows Subsystem for Linux GUI
#135Earlier quoted context omitted.
The amount of effort that went into WSL1 including the number of bug-for-bug changes involved was tremendous. It blew my mind when WSL2 was announced because the hyper visor approach was already possible (and in use) before WSL1 was announced but MS made an explicit decision to do the extra work to make their own Linux subsystem for Windows the harder/better way… then gave up.
They were amazingly successful -- more successful than should have been thought possible -- but they couldn't overcome the semantic file system differences.
Re: Windows Subsystem for Linux GUI
#136> Please note that for the first release of WSLg, vGPU interops with the Weston compositor through system memory. If running on a discrete GPU, this effectively means that the rendered data is copied from VRAM to system memory before being presented to the compositor within WSLg, and uploaded onto the GPU again on the Windows side. This is a pretty big limitation. Hopefully it can be addressed soon.
Re: Windows Subsystem for Linux GUI
#137Earlier quoted context omitted.
Accessing the Windows filesystem from WSL and vice versa is extremely slow, so running for example your IDE in WSL and having your code etc. stored in WSL is useful. I think that is one of the big usecases. It's already kinda supported in vscode, where it runs a vscode server in WSL and Windows just runs the frontend. It's useful for me when developing dotnet intended for Linux as I can store the code in WSL and be a…
Are you talking about WSL1 or WSL? Wsl2 is much much faster due to having a virtualized real linux kernel running
Re: Windows Subsystem for Linux GUI
#138How is this better than just running vcxsrv and inside WSL setting DISPLAY=WINDOWS_HOST_IP:0? I've been doing this to run graphical linux apps for a couple years now, both on WSL1 and on a regular Hyper-V Linux VM.
Re: Windows Subsystem for Linux GUI
#139Earlier quoted context omitted.
As the author of EasyBCD, I can tell you that interest in dual-booting has collapsed to near zero over the past decade.
How much of that effect do you think is due to recent Windows versions not playing nicely so you still get some hassle anyway and/or to improving options to run Windows virtually on a Linux host with close to native performance and compatibility?
Re: Windows Subsystem for Linux GUI
#140[0] https://github.com/microsoft/wslg/raw/main/docs/WSLg_Integra...