While it actually works, there are truly some missing features obviously. The hope is, when lot of major distributions and desktop environments stop supporting X11, then application developers and Wayland developers have to find a solution quicker. This will accelerate development of Wayland, at least the remaining issues.
One area where Wayland needs to improve is support for various accessibility features.
That does feel rther like jumping out of a plane and hoping you can finish making your paracute before it’s too late.
The concept of moving on from X11 is a good one, but making Wayland just a protocol that every compositor has to implement separately, and having so many optional larts to the spec seems like a guarantee that the ecosystem around it will never properly mature.
The KiCad developers have a good article about some of the issues with Wayland here.
I actually see this working out in the long run at least. In the mean time, there will be a lot of creativity while everyone tries to “invent the wheel” while great ideas perculate up during the stabalization phase.
This is big “if we break your old toys, you’ll HAVE to play with the new ones” energy.
Tell me when they port FVWM. Seriously. FvwmButtons-- a pretty trivial dock except it can swallow other windows-- seems like it would be out-of-bounds on Wayland unless it was owned by the compositor itself to access the other windows. I don’t see any of the new taskbar-tools used with Wayland compositors offering similar functionality (I could be wrong) and that seems an amazing loss of feature parity.
While it actually works, there are truly some missing features obviously. The hope is, when lot of major distributions and desktop environments stop supporting X11, then application developers and Wayland developers have to find a solution quicker. This will accelerate development of Wayland, at least the remaining issues.
One area where Wayland needs to improve is support for various accessibility features.
That does feel rther like jumping out of a plane and hoping you can finish making your paracute before it’s too late.
The concept of moving on from X11 is a good one, but making Wayland just a protocol that every compositor has to implement separately, and having so many optional larts to the spec seems like a guarantee that the ecosystem around it will never properly mature.
The KiCad developers have a good article about some of the issues with Wayland here.
I actually see this working out in the long run at least. In the mean time, there will be a lot of creativity while everyone tries to “invent the wheel” while great ideas perculate up during the stabalization phase.
Oh wow. I am suddenly less excited about our Wayland future.
Damn yeah. Just the window managment issues are a complete no go for any productive work.
This is big “if we break your old toys, you’ll HAVE to play with the new ones” energy.
Tell me when they port FVWM. Seriously. FvwmButtons-- a pretty trivial dock except it can swallow other windows-- seems like it would be out-of-bounds on Wayland unless it was owned by the compositor itself to access the other windows. I don’t see any of the new taskbar-tools used with Wayland compositors offering similar functionality (I could be wrong) and that seems an amazing loss of feature parity.