Quite literally, the only problem or “stuff broken because or Wayland” is some old ass apps or lazy companies that won’t update their electron version. Looking at you discord, screen sharing COULD WORK if you managed your stuff
KDE gui scaling problems too?
Kinda. The problem was fixed in Qt6 and current KDE is Qt5. It’ll be fixed once Plasma 6 releases in February.
I really don’t like nate’s take here. IMO it’s really not that good, Wayland is still outright lacking features, even when using the craptastic xdg portals junk
X11 has it’s own issues (and there are a lot of them, including security)
What features exactly?
I didnt even remotely imply that x11 doesn’t have issues, so im not sure why that was brought up. The goal is to make wayland an acceptable and universal replacement, Everyone knows x11 is dying but wayland isnt ready to replace it yet
Things like window embedding, the wayland way is for each app to have it’s own embedded compositor. Wayland has no support for things like overlays/always on top (Useful for OSKs PR has been made but like all wayland things, we might not get it for another couple years, or perhaps never), currently missing support for reading other window states (PR made for this as well, but again, who knows how long it will take), Still no support for window positioning (again PR made), Emulated input events (libei is not universally supported) And these are just the ones off the top of my head, There were others but I cant think of them ATM
“not everything is fully ported yet”
“There will probably be an awkward period before all of these pieces are in place for all of the people.”
I think these are the two key takeaways – Wayland is still in development and the bandwagoning are the early adopters – most of us will switch when our distros switch (and will probably be none the wiser)
the problems (and the reason we’re suffering through sensationalist stuff like “Wayland breaks everything!”) is the fanboy push to switch before it’s ready – not everybody lives on the bleeding edge (just like not everyone runs Arch) and the “switch now or be left behind” attitude does more harm than good (far more likely to alienate than convert) …
Wayland != X11
Not 100% feature compatible != broken.
My opinion and also a TL;DR: of the article.
“that thing you used to do is now impossible to do consistently across different implementations, if at all. But it’s all ok, because we have decided it’s not our responsibility!”
That is not what users want to hear. From a user’s point of view, it is broken.
I see what you’re getting at. It’s a matter of perspective, I guess.
If you presented someone with a list of features from two similar but different pieces of software, they wouldn’t say software b is broken because it’s featureset is different from software a, right? But I acknowledge it’s not that straightforward. It’s more like telling them software b is going to replace software a that you’re currently using, get ready to say goodbye to some features.
I still don’t consider wayland broken, but I understand argument that it is.
yes, if i combare kicad with blender, neither is broken because they have different features. But also, nobody is telling users that kicad’s days are over and it should be replaced by blender. If they did, and a user wanted to design a circuit board, the user is out of luck. The user is told that it is a replacement. From the user’s point of view it most definitely is not.
The probeem isn’t just that wayland doesn’t do everything x does. But that users are told that it will replace x, deal with it and quit complaining.
We have to keep in mind that the fact that we know what wayland is in the first place puts us squarely into the “technical user” category, not regular users. Regular users are the ones who don’t even know (nor should they have to care) what wayland even is
