Fresh Wayland rant
@emersion I'll agree with you that yelling at maintainers is an absolutely awful thing to do and is totally unacceptable.
I think part of the reason you see this though is that people keep getting told Wayland is a replacement for X11. By design Wayland will never replace much of what X did. There are also a number of design trade offs where the downsides are more or less unacknowledged. Compositing is a big one: many use cases are very latency sensitive, many users would much rather have tearing than wait a frame or two for updates.
The distros making Wayland the default before it was ready didn't help either. There are lots of "I don't want to think about configs so I'll just run Ubuntu" people that I know who have actually gone through the trouble of installing an X11 DE just to get most of their apps working without hassle again. It's not that they don't work in Wayland, but they don't work well with the default configuration *today* which is what the "I don't know or care how it works" group of people get so upset over.
Fresh Wayland rant
@swiley As for the rest, yes, that's bad. Partially gnome's fault, partially the distro's fault.
However, the author's problem was with people harassing people writing wayland code and spreading misinfo about it, when it's somebody else's problem.
Fresh Wayland rant
@swiley >many use cases are very latency sensitive, many users would much rather have tearing than wait a frame or two for updates.
You don't have to wait a frame or two to have vsync. Only if you do it the naive x11 compositor way.
If a frame takes 5ms to render in full, simply start rendering it 6ms before the buffer swap, you get 1ms latency and vsync.
It's not inherent to not having tearing that you have 33ms lag.