picom VS sway

(https://github.com/yshui/picom/blob/next/picom.sample.conf)

Also I took a census and zero founding members of NWA are "straight outta Picom". That's right, you heard it here first: Not even MC Ren is running Picom.

Update: after reporting in picom GitHub repo this is temporarily solved by using --no-frame-pacing. Looks like a recent commit causes this. You can view the discussion here: https://github.com/yshui/picom/issues/1072

NEED HELP TESTING (write your issues here): https://github.com/yshui/picom/issues/1052

Compositor : picom

It looks like this was identified and the repo corrected in Jan (https://github.com/yshui/picom/issues/808) but the NixOS package has not been updated since Nov.

If you have compositing you are likely using picom. You can check if it's running with ps -A | grep picom. I've never dealt with this issue as I don't really game on linux often, but I'm sure there's a solution somewhere in the github docs or issues. Worst case scenario you could always just kill the process with killall picom whenever you're about to game, and re-enable it with picom -b after. Do note though that currently running windows might bug out a bit when you kill/start the compositor.

Picom is broken for me with GLX backend related Github issue.

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).