WSL VS wslg

There have been massive GitHub issue spams recently, including in Microsoft's WSL repository.

https://github.com/microsoft/WSL/issues/40028

Reference: https://github.com/microsoft/WSL/issues/12586

The Windows filesystem isn't slow per se, it's a slowness caused by "a thousand cuts" type of problem.

https://github.com/Microsoft/WSL/issues/873#issuecomment-425...

You might be missing context here.

There is a feature of Windows called “Windows Subsystem for Linux (WSL)” already that basically does the inverse of this (windows host, Linux VM).

https://github.com/microsoft/WSL

The feature is a windows subsystem (for running Linux).

I mean inside WSL. E.g. running nested virtual inside WSL env. https://github.com/microsoft/WSL/issues/11216#issuecomment-2... for details.

I use a WSL backend and there seems to be some issues with file watching (You can read more about it here and here). This means that automatic recompilation on save does not work, this is why I add the --manual-run flag in the initialization. On other systems this might work without issues.

👉 Baixar WSL 2.3.24 (MSI)

Microsoft's WSL2 GUI integration works based on Wayland (and XWayland): https://github.com/microsoft/wslg

Rather than going fully protocol-based (like Waypipe), they used Weston to render to RDP. Using RDP's "remote apps" functionality, practically any platform can render the windows. I think it's a pretty clever solution, one perhaps even better than plain X11 forwarding (which breaks all kinds of things like GPU acceleration).

*Yes, I know, WSLG exists and is actually goated...

> It's an absolute delight to use, out of the box, on a desktop or laptop, with no configuration required.

I have been using it since the beginning of WSL 1 with a very terminal heavy set up but it has some issues.

For example WSLg's clipboard sharing is buggy compared to VcXsrv. It doesn't handle pasting into Linux apps without introducing Windows CRs. I opened an issue for this https://github.com/microsoft/wslg/issues/1326 but it hasn't gotten a reply.

Also, systemd is still pretty sketchy. It takes over 2 minutes for systemd services to start and if you close a WSL 2 terminal for just a few minutes systemd will delay a new terminal from opening for quite some time. This basically means disabling systemd to use WSL 2 in your day to day.

Related issues:

https://github.com/microsoft/wslg/issues/1008

WSLg[1] is Microsoft's first-party solution. It's interesting because it uses RDP as the display layer.

[1] https://github.com/microsoft/wslg

As far as I know it only supports basic tapping/clicking for GUI applications and not multi-touch or gestures.

https://github.com/microsoft/wslg/issues/737

WSLg(Windows Subsystem for Linux GUI) uses RDP and FreeRDP to work: https://github.com/microsoft/wslg

I haven't tried it yet, but I'm hopeful the experience is better than last time I tried Hyper-V enhanced linux experience. I imagine this use case is getting FreeRDP way more attention.

For years I've developed in a Linux VM on a Windows host via VirtualBox. The typing lag on this, particularly in IDEs like VSCode and Rider, finally got to me. So, I moved over to WSL and have to say; the experience is amazing.

This is running in WSL?

Microsoft has some wayland stuff already for WSL, though I think internally there's RDP involved: https://github.com/microsoft/wslg