I WILL continue to use Xorg. My workflow requires it. If that means I have to use an unmaintained window manager forever, so be it.
None of this would be an issue if the Wayland developers weren’t so pigheaded that they insist upon forcing their pure, untainted design philosophy onto the project rather than building an inclusive model that allows for backwards compatibility with the system it’s meant to replace.
building an inclusive model that allows for backwards compatibility with the system it’s meant to replace.
That’s honestly a terrible approach and defeats the porpoises. For example, screen recording. You can’t be “backwards compatible” (aka any app can record at any time) and have them ask for permission (the honestly better way to go).
Bear in mind, Wayland devs didn’t force anything. They offered an alternative to X and the distros chose that after evaluating pros and cons.
Pick a distro that aligns with your needs like we all do.
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 am not better served. I am now in the quite new position where I’d have to rewrite some of my own personal software if i simply just decided to change DE
I WILL continue to use Xorg. My workflow requires it. If that means I have to use an unmaintained window manager forever, so be it.
None of this would be an issue if the Wayland developers weren’t so pigheaded that they insist upon forcing their pure, untainted design philosophy onto the project rather than building an inclusive model that allows for backwards compatibility with the system it’s meant to replace.
That’s honestly a terrible approach and defeats the porpoises. For example, screen recording. You can’t be “backwards compatible” (aka any app can record at any time) and have them ask for permission (the honestly better way to go).
Bear in mind, Wayland devs didn’t force anything. They offered an alternative to X and the distros chose that after evaluating pros and cons.
Pick a distro that aligns with your needs like we all do.
i’m just curious what is the feature you are using in xorg you can’t replicate in wayland?
Activity watch
Not who you asked, but:
sxkhd: no global hotkey daemons allowed except the compositor
i3wm inside of xfce/plasma: every compositor is implemenyed as a monolithic DE, fuck modularity
I still switched to Wayland, but can’t be bothered to customise a new wm
Can you use Sway instead of i3wm in plasma?
No
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 am not better served. I am now in the quite new position where I’d have to rewrite some of my own personal software if i simply just decided to change DE
That sounds like a fairly niche problem to have.
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
Then, build your own replacement! If it is do dinpley, fork Wayland, add what you need.