wslg VS sway

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

That said. Graphical apps will just run on WSL without needing to install anything. Check: 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

See: https://github.com/microsoft/wslg/issues/563 and other similar issues on wslg GitHub.

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

Here’s a thread about it. You can get into the underlying RDP session instead of just apps launching. https://github.com/microsoft/wslg/issues/1019

This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.

I also have crashes on sway, but there’s a rough workaround now which prevents the issue totally.

I believe there’s a design issue with Firefox and GTK handling input events; some Wayland compositors have workarounds but others do not.

https://github.com/swaywm/sway/issues/7645

https://bugzilla.mozilla.org/show_bug.cgi?id=1743144

Firefox is my preferred browser and I hope we can keep its engine alive in this era of Chrome dominance.

I'm seeing this: https://github.com/swaywm/sway/wiki/Setting-Environmental-Variables but I haven't figured out how to make GDM do it, and I was wondering if there was a super simple "HEY SWAY READ MY .PROFILE" thing I could do.

So I searched around and found the following bug report where this problem and a possible solution was borough up: https://github.com/swaywm/sway/issues/2966 , which was then immediately closed again.

I've been using Sway since late 2019. I like the workflow of a WM. I honestly find it hard to go back to a DE, I like having a minimalistic desktop.

Sway is fast, minimal, and flexible. Their recommended tools/addons are worth a look: https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway

From that list I use greetd + tuigreet as my login manager, sway-launcher-desktop for FZF-powered app launching, and wob for lightweight brightness and volume display (send '50' to the wob socket and it'll show 50%; it doesn't get simpler).