goomwwm VS mutter

I used to love GOOMWWM[1] and used it for the longest time. I miss a lot of things about it, still. It doesn't quite meet your requirements, looks-wise its very minimal and it doesn't have snapping, but I really liked the idea behind it: make a keyboard-centric stacking/floating window manager that gives you enough control that it can be used as if it were a (manual[2]) tiling window manager. It really feels like a tiling window manager and its fantastic!

[1] https://github.com/seanpringle/goomwwm

[2] I personally use sway these days, but I still prefer manual tiling where I move and size windows myself, rather than having the WM try to do it for me, as long as the WM makes it very easy to do, as goomwwm did (and its predecessor, musca: https://github.com/enticeing/musca)

I came to filing window managers through musca[1] and then goomwwm[2] (Get Out Of My Way Window Manager) and then switched to i3 (and more recently, away) because both Musca and goomwwm haven’t been updated in years.

I still miss Musca and goomwwm. They didn’t require any visualisation of the hierarchy, things were just layer out next to each other without a hierarchy and just worked. It was very intuitive. Goomwwm went a step further: it’s not technically a tiling window manager at all, but rather a floating window manager (so you can have your windows overlap if you want) that happens to be usable as if it were tiling and that’s keyboard centric (but you can use mouse too if you wish). That really was the sweet spot for me and I often find annoying behaviour in i3/sway that goomwwm didn’t have (typically around movement and resizing).

[1] https://github.com/enticeing/musca (original source and all documentation seems to be gone)

[2] https://github.com/seanpringle/goomwwm

Kewl. I guess the bug report should go to https://gitlab.gnome.org/GNOME/mutter

Regarding Ubuntu Gnome Wayland, I heard that there is the possibility to get VRR working with mutter-vrr (and gnome-control-center-VRR ?) https://gitlab.gnome.org/GNOME/mutter

You should create an issue in https://gitlab.gnome.org/GNOME/mutter for this.

As a result I'm studying the wayland architecture (I like gnome so the compositor would be Mutter) so that I can figure out how to either make a hack or make something legitimate. This is proving time consuming.

Hmm.. I'm not sure about the negativo drivers, but if you need EGLstreams working it seems like there are a few build options for mutter you can use? https://github.com/GNOME/mutter/blob/main/meson_options.txt

pkgname=mutter pkgver=42.0 pkgrel=0.1 pkgdesc="A window manager for GNOME" url="https://gitlab.gnome.org/GNOME/mutter" arch=(x86_64) license=(GPL) depends=(dconf gobject-introspection-runtime gsettings-desktop-schemas libcanberra startup-notification zenity libsm gnome-desktop upower libxkbcommon-x11 gnome-settings-daemon libgudev libinput pipewire xorg-xwayland graphene libxkbfile libsysprof-capture) makedepends=(git gobject-introspection egl-wayland meson xorg-server wayland-protocols sysprof) checkdepends=(xorg-server-xvfb wireplumber python-dbusmock) provides=(libmutter-10.so) groups=(gnome) _commit=9249aba72a5c4454894c08735a4963ca1665e34d # tag/42.00 source=( "git+https://gitlab.gnome.org/GNOME/mutter.git#commit=$_commit" "https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441.patch" ) sha256sums=('SKIP' 'SKIP')

Mutter

Wayland is a protocol - not an implementation. It tries to minify latency by merging together some of the components X11 had and tries to do this in a slim and faster way.

The implementation of the protocol may differ, but I know for example MUTTER (https://gitlab.gnome.org/GNOME/mutter)

This article has nice and not too complex visualisations: https://www.secjuice.com/wayland-vs-xorg/

Stock Mutter - in contrast to this fork of it - would not work either.