You're viewing a single thread.
for them to admit that wayland is just not ready. Get feature parity first, then switch.
X is not ready. I am running X and it doesn't do vsync properly on the desktop or browser
I use Wayland on the daily and don't have any issues with it. What problems are you having?
it crashes daily (I have nvidia, true, but so do the majority of people, so i expect it to work before being forced on me). As a user, I do not give a fuck whose fault that is, (LOTS of fingerpointing going on there) but if it's not stable, then don't force the switch to it yet.
Does it have soome new features? Yes it does, but what really affected me is the features that are removed, by design. Some apps don't work properly on wayland because it does not allow them to do what they need. And if you complain that something does not work, you'll be told that you don't need it and you will like it.
Also, far too much stuff is "not wayland's responsibility". Which means that one cannot just write an app for wayland, but rather for kde on wayland, or for gnome on wayland, etc. So if, as a dev you ask, for example, "how do I take a screenshot on wayland" you get the response "that is not something wayland does, check your de, compositor, one of the bunch of incompatible implementations", for functionality that had been seamlessly available and taken for granted on every single os I tried (including linux, with x).
And I hate being told you can't do that because it's not secure. It's my machine running my code. Stop forcibly protecting me from myself. Turn some functionality off by default? that's fine. cater to the average user. Promising to never implement the functionality because I might hurt myself if I don't know what I'm doing in not ok