sway VS weston

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

I decided to investigate how different Wayland client implementations behave with cursor scaling across 4 different Wayland compositors at different scale factors to get an overview of the situation. Below are my findings. As you can see, cursor scaling on Wayland is messy, with the reference Wayland compositor implementation Weston performing the worst. If you find my data to be incorrect please provide your findings in the comments.

Mutter is not the “official Wayland implementation”. Wayland has one reference implementation: Weston https://gitlab.freedesktop.org/wayland/weston

If you want Wayland, labwc (GitHub link) aims to be very close to openbox, so it should pop in pretty easily. That being said, Weston (Gitlab link) seems like the best implementation of a wayland compositor right now.

Weston is a simple wayland one. Wayland does basically what X11 does, but wayland is the modern one that X's legacy baggage: X11 even printing directly part of it.

For example code there is the weston repository.