As a developer, I really don’t like how Wayland has fractured the ecosystem. Competing immature protocols are still all over the place while the immobility of x11 has spoiled us for years. It’s getting better, but in the meantime I can still write an x11 app which will work mostly everywhere (thanks to xwayland), whereas a wayland app may not work everywhere (not on X11, and not on compositors which don’t implement the right combinations of protocols).
As a user I like no screen tearing, low latency, no soft locks from apps crashing, no softlock when a window is capturing the keyboard while the screen is locked, no weird artifacts from hardware accelerated effects, no app windows blanking out and lagging usually web apps (still happens in XWayland),etc.
I still miss being able to kill the screen locker from the terminal, made me feel like a hacker.
As a developer, I really don’t like how Wayland has fractured the ecosystem. Competing immature protocols are still all over the place while the immobility of x11 has spoiled us for years. It’s getting better, but in the meantime I can still write an x11 app which will work mostly everywhere (thanks to xwayland), whereas a wayland app may not work everywhere (not on X11, and not on compositors which don’t implement the right combinations of protocols).
As a user I like no screen tearing, low latency, no soft locks from apps crashing, no softlock when a window is capturing the keyboard while the screen is locked, no weird artifacts from hardware accelerated effects, no app windows blanking out and lagging usually web apps (still happens in XWayland),etc.
I still miss being able to kill the screen locker from the terminal, made me feel like a hacker.
@[email protected]
wayland sux
😂