cbl-mariner VS wslg

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

What are you talking about? Its free forever https://github.com/microsoft/wslg

Actually, you can https://github.com/microsoft/wslg

Apparently, WSLg does away with the need for a separate X server, making things "easy" to use:

https://github.com/microsoft/wslg

There's two completely different aspects to your question. 1) How to manage libraries in c++ without dying from cringe? I'd suggest you use cmake as the build system and grab library sources directly from GitHub using this tool: https://github.com/cpm-cmake/CPM.cmake 2) How to get apps that run under WSL to display windows-native windows? I'm not sure, but it's probably this: https://github.com/microsoft/wslg

Install WSL2, install docker there and phpstorm, use x410 or any xserver or microsoft one https://github.com/microsoft/wslg.

It actually works with native apps. It has also opengl acceleration normally: https://github.com/microsoft/wslg

If you're new to WSL as I am, you'll marvel at graphical apps "just working", appearing as normal windows getting along like any other app. Under the hood, this isn't entirely unlike running a VM in "seamless mode". There are a few paths WSLG can take to make this happen, some better than other. If you have a linux GUI app running and open the windows "Task view" (by pressing Windows + Tab or whatever), if you see a "WARN: COPY MODE" label atop your linux apps, WSLG is being forced to use a slow path to render areas to screen. The exact reasons why escape me. An older ticket recommended installing an updated Mesa package to get to Mesa 21.x, but new WSL 2 installs are already there. Nonetheless, I followed those steps, ended up with Mesa 22.2.4, restarted WSL and the warning went away, replaced by a much higher refresh rate for linux windows (easy to check if you just drag a linux window around.) Notably, the warning came back once later, with scary logs in /mnt/wslg/weston.log about shared_memory errors, but restarting Windows made things better again.. YMMV.