I mean stuff like bugs with boot screen leaking data not being fixed with X and so on.
Re:Wayland on OpenBSD
by badsectoracula on Tuesday July 11, 2023 @06:07AM
(#36678773)
How does that have anything to do with X not keeping up with new hardware or using the same kernel APIs as Wayland for communicating with said hardware?
What you describe is a minor annoyance at most, not at all on the same level as being unable to use X because of newer hardware. Even if it isn't fixed, one can still be worked around or just ignored, but the other just makes the whole thing literally unusable.
That means that X case will become increasingly broken. It won't work and won't be supported, newer hardware or not.
And X won't have parity for hardware features anyway. Like HDR - it will be Wayland only. And so on and so forth. So X is fried on all ends in the long term.
It's not that it's not possible to use kernel interfaces - it's just no one will bother putting an effort in developing X because it a waste of effort. It's already happening.
What exactly do you refer to? Note that i meant the kernel APIs to drive the hardware as what i replied to was Xorg not keeping up with newer hardware, not toolkits.