"After a bit of discussion on HackerNews, I got a bit better understanding of the actual problem. People don't want to just configure the keys according to a particular layout - the actual 'issue' here is that they expect the key binding changes together with the layout. Unfortunately, the 0.8.0 changes didn't make this possible to implement as a plugin.
I would reconsider adding this as an option if there are enough interested people. React with a thumbs up to this comment if you are interested in having this option (though the defaults will certainly remain as they are now). Please, react only if you actually use Wayfire or would use it if it had this feature :)"
https://github.com/WayfireWM/wayfire/issues/1601#issuecommen...
The issue is that people expect "KEY_Q" to refer to the key that inputs a "q", no? Classic desktop-Linux-level user friendliness.
I believe this is the compositor they're going to run on Raspberry Pi 4 and 5 with the next OS release, so it makes sense it will run on more limited hardware.
I've wanted this for 7 years
Is there a good story behind how specific that is?
I'm happy it's alive because I find it to be a great and hugely underrated compositor with great potential.
> Wayfire is a wayland compositor based on wlroots. It aims to create a customizable, extendable and lightweight environment without sacrificing its appearance.
Now a visitor should know what "wayland" is, and then what a "wayland compositor" is, and only then can they decide if the project is interesting. The description assumes this knowledge, but many people will not take the time to figure it out and just surf to the next interesting thing. Opportunity missed.
You might even have a short bullet list of reasons to use it rather than just a tagline.
This IPC is a custom built IPC that has no security. This means that any program can do stuff like steal focus or drive other window manager policy if the plugin is there. There is also a plugin that exposes the ability to send key or mouse events.
Applications should just use DBus instead of creating their own custom IPC protocols just because they feel like it.
When I start seeing C++, AUTH, and Kerberos I start getting concerned.
When I don't find a Python-only module for something claimed to be "simple", I start getting very concerned: https://pypi.org/project/dbus-python/
In this specific context it is less about being better and more about being the standard for apps that are part of the Linux desktop except for Wayland which has its own. There are benefits in developers all being familiar with dbus, not having to use different clients for each program you want to talk to, it is easier to secure, etc.
Personally, I prefer IPC because it is simpler to implement, debug and use.
Wayfire is a living space I can tinker with.
In wayland-land the only one I managed to use for a couple of days without crashing was sway in 2022. Both their last release and sway-git is crashy
