I just recently tried to switch to sway. If you have a 4k display, prepare for all your xwayland programs to be rendered 2k and upscaled.
Other wm have a workaround for that, but sway devs just completely dismissed the problem.
I just went back to i3, but that probably means I have to look for something else to switch, which sucks, because it changes my workflow…
I can absolutely see what that dev means. One of the most frustrating thing about Wayland is not that bugs just don’t get filed or you are the first to stumble over an issue. Every single issue I discovered that prevents me from finally making the switch (and yes I try, I’m not married to X11) always ends up being an already open issue for multiple years, even with people providing implementations or fixes, but some person just blocking it for various reasons.
And almost always it’s some form of perfectionism from people who probably have all the best intentions and “just want to do it right this time”. So we don’t end up with jet another pile of unmaintainable extensions. And the same people then get frustrated if users mention that things still don’t work for them.
In the end this indecisiveness will just lead to an even more fragmented situation in the sort term, with every compositor implementing their own workarounds (at least the ones who care about things actually working) and the “standards” being set that way.
If I had to guess, I would say we will see an even stronger shift of the community towards KDE, because this are the people who actually seem to care that things work for their users right now and just go ahead and implement those workarounds.