I will concede that not every obscure feature has been kept but the vast majority of users are now better served by wayland compositors. I have no idea what you mean by “project”, but if they had no concerns for backwards compatibility, then XWayland wouldn’t exist.
Stopping work on X11 because it’s been an unmaintainable mess for ages doesn’t really count as “forcing” anything upon anyone. I won’t pretend that Wayland protocol development hasn’t seen plenty of disagreements, but it is still a collaborative process.
Your disagreements seem fairly vague to me and I can’t help but think that the “pigheaded” label is somewhat ironic, after your first paragraph.
I will concede that not every obscure feature has been kept but the vast majority of users are now better served by wayland compositors. I have no idea what you mean by “project”, but if they had no concerns for backwards compatibility, then XWayland wouldn’t exist.
Stopping work on X11 because it’s been an unmaintainable mess for ages doesn’t really count as “forcing” anything upon anyone. I won’t pretend that Wayland protocol development hasn’t seen plenty of disagreements, but it is still a collaborative process.
Your disagreements seem fairly vague to me and I can’t help but think that the “pigheaded” label is somewhat ironic, after your first paragraph.
There is currently one major Usecase that does not work yet with Wayland. Multiwindow positioning through the application.
In science, and some stuff like KICaf or Gimp use this feature excessively. And as someones that relies on KiCad, it is a fucking pain.
But, solutions are being discussed and implementations will follow