On 2025-09-17, Alexis wrote: > Dale <[email protected]> writes: [...] > >> For the record. I'm not against Wayland. It's just not ready for >> my >> use yet. > > Disagree. > > My experience has been that statements like this aren't helpful, > because people assume "Not ready for my specific use-case(s)" means > "Not ready for anyone's use cases". That's a strong claim, and > demonstrably incorrect. And it goes both ways: there are people for > whom Wayland is a significant improvement over X, and so say to X > users, "No, you're wrong, it _is_ ready." But again, that's incorrect; > different people have different use-cases.
Eh, no, it'd be much more valuable to know why someone says Wayland isn't for them, at all or yet, than to try to avoid making such objective remarks just because there's a risk that gets misinterpreted. If someone overreacts because they read "it doesn't work for my use case" as "nobody should use it", it's not really the person who wrote the former who should adapt. > i started doing my own investigations for Wayland because i realised > that it's coming down the pipe, and i wanted to add and update the > wiki's information about Wayland, to make sure that it's factually > correct. There haven't tended to be enough volunteers willing to work > on maintaining X, until the recent appearance of XLibre; most of the That's something I haven't had time to check further, but which sounds slightly off, because NetBSD has been doing their own modifications to Xorg. https://blog.netbsd.org/tnf/entry/x_org_on_netbsd_the -- Nuno Silva
