There has been a tremendous amount of noise given the @kicad decision to stick to #X11 for now. A lot of inaccurate debate about missing features of #Wayland especially related to input keymaps. So here a thread:

First of all keymaps are handled, by libinput, this is the same in X11 as in WayLand. Its just that in X11 you have dedicated binaries to communicate with the keymap backend but these are essentially wrappers.

Most WayLand Compositors and window managers allow to pass keymap configuration, not just #KDE or #Gnome.

Back in the day these binaries where needed as we had 100x input backends, now a days its all libinput.

Second, @kicad deciding to stick to X11 in no way shape or form impedes you from using it on Wayland!

I can't stress this enough, #kicad works absolutely fine using #xwayland so you shouldn't even get riled up over this.

@dantalion @kicad But KiCad isn't "sticking to X11".

People thought it was "KiCad sticking to X11"? The blog post was "KiCad works on Wayland, we just can't fix these issues for you as they are out of our hands" and "Use X11 if you are bothered by these unfixable issues".

;)