i3 VS wslg

While I believe Memory Saver was a great improvement, it only works if the tab is hidden or the window minimized. I recently learned the required state is not triggered if the tab is open but on another virtual desktop. At least this is the case with many of not all Linux window managers. Some of the many discussion threads on the topic:

https://github.com/i3/i3/issues/4353

> This is very true, and unfortunately there are very few people working on linux accessibility (including not me! I am part of the problem!).

Accessibility work itself ironically suffers from an accessibility problem. I brought up i3wm above, the issue for that is pretty illuminating: https://github.com/i3/i3/issues/3393

It's not that the devs are saying "this doesn't matter", the devs behind one of the most popular tiling window managers in the X11 ecosystem are saying, "this does matter, but we don't know how to fix it. We don't know what changes we'd need to make to get Orca working."

It's a really fundamental breakdown that's kind of a tragedy because I honestly believe that if accessibility communities were more heavily baked into testing and development in Linux and if this wasn't treated like two separate worlds, it would be better for everyone -- fixing accessibility concerns very often improves interfaces across the board and makes them more powerful.

But... how do you bridge that gap? I don't really know, I tried looking into Orca to see what would need to happen here and bounced off of it pretty hard, it's not a very approachable tech stack and there aren't tutorials or getting started guides. And on the other side of the issue I can preach about needing accessibility input during interface design, but I'm not in a position to give specific advice because I don't use screenreaders or alternate control schemes and I don't know what the biggest problems are.

The people who need to be involved in that process can't get involved because there's a tech barrier in place even for technically inclined people, and because the underlying software locks them out from the start. i3wm isn't ever going to get someone who's intimately familiar with Orca to jump into the conversation because the people who need to use Orca can't use i3wm. So that leaves the people who can address that tech barrier, but they don't know what to do or how to approach the problem because of the lack of involvement and because the communities are isolated from each other. So it's a chicken-and-egg problem and I don't know how to solve it.

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.

for example, take i3. https://github.com/i3/i3/issues/4478

Some window managers are meant to be used as-is, and provide a minimalist yet functional environment that use very little resources or give power users an almost HUD-like interface. Examples of those window managers are OpenBox and i3wm for X, and Weston and Hyprland for Wayland

i3, https://i3wm.org

I did use i3 exclusively for a few years. The reasons I chose it were

I don't think you can with base i3. See this open issue on the subject: https://github.com/i3/i3/issues/1129

well, it depends. It was better experience than FreeBSD 7.2 that's for sure. :) It was running Xorg with https://i3wm.org, a web-server, XMPP-server, PostgreSQL, few bots and dovecot / postfix (e-mail server). It was doing fine routing internet for 2PCs and a WiFi router for 10 years until its HDD died. For gaming... erm... I was able to play something like Theme Hospital or Syndicate Wars in dosbox. You have to understand any OS is just software it doesn't make magic. With minimalistic Desktop Environment like Xfce, LXDE or even barebones i3wm you can put your hardware to use with Arch Linux.

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.