Some issues with Wayland explained.
Well, I switched to Wayland (sway) exactly because mpv could not do vsync with X11. So I guess frame callback is how you get vsync working by default and client timing loop is how you get no vsync by default. And getting the other than the default thing is always a major hack - in last 20 years I wasted days trying to get X11 do proper vsync and it never really worked and probably will never do work.
Another think is that in one paragraph the complaint is that Xorg supports to many features and on another that Wayland is slow to adopt and requires justification for adding more features… so have cake and eat it too?
Also please don’t complain about missing features when you know they are not there just because the thing did not get all the development time the other thing did… unless stuff is broken by design/culture (like with the scale factor it seems).
I too switched to sway because any X11 compositor I’ve tried over the past few years I could never get vsync properly working. I have multiple monitors one of which has a different refresh rate. The mixed refresh rates actually makes X11 compositors constantly use up 10-20% of my CPU. And when I turn V-sync off my GPU starts sweating really bad for some reason. Wayland literally has none of these problems.
The thing with these kind of arguments is that they don’t really matter. You have thousands of volunteers working on these projects. If they collectively decide working on software A isn’t fun anymore, you either pick up the slack on software A yourself or you hopefully enjoy software B.
