While I appreciate all the folks singing our praises, as an upstream developer I think you deserve a better response than "you are holding it wrong" :)

We think that the Wayland session currently is the better choice for the majority of our users. It's more stable and polished, performs better on average, and has more features and enables more hardware.

That said there are still gaps in the experience, and non-latin input is one of them. In principle it's roughly on par witu X11, but it's still pretty crap, e.g. at the moment we give you a choice between having a virtual keyboard and having something like ibus active, when many users want both at the same time, and a lot of the non-latin setup stuff is still not part of the core product, which is very user-unfriendly.

The KDE Linux alpha in particular will definitely and unequivocably not serve you well as it currently doesn't ship any ibus/fcitx.

The good news is that this is something we are very actively working on in the background right now. We have an annual community-wide goal election process that made Input improvements one of our goals, and the topic has been all over our developer conference this year.

Another huge gap is accessibility. No wayland compositor has managed to implement screen reader support that works with existing applications yet. And no, GNOME's wayland compositor did not achieve this. In typical GNOME fashion they threw away all support for existing screen readers and accessibility and invented two entirely new GNOME only protocols that no software except theirs supports.

Can I do something like `wmctrl -xa terminator || exec terminator` yet?