El 18/9/25 a las 3:16, Alexis escribió:
Nuno Silva <[email protected]> writes: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.As i wrote in the post in which i apologised for my mistake, i wasn't reading it that way, because what i was actually seeing on the screen was "It's just not ready for use yet", not "It's just not ready for _my_ use yet". It wasn't about me misinterpreting the latter sentence. And as i also said in that same post:i constantly see people claiming "Wayland is not ready for prime time yet", purely on the basis of it not being ready for _their_ specific use-case(s).That's the necessary context for my response. i wasn't responding in isolation from the behaviours of people from various sides of the Xorg / Wayland debates i regularly encounter across the 'net. And even if the premise on which i'd written my comments wasn't correct, i believe the comments themselves still stand.Alexis.
There is not wayland vs xorg debate since there are not wayland users, just wayland xorg driver users and I doubt that this would change since a lot of software lacks wayland support and requires to run Xorg glue wayland layer
So, people that says I'm a wayland user and I'm really happy doesn't know that they are using xwayland xorg display driver to be able to use software as avidemux.
No debate, since actual wayland users are just Xorg users that uses wayland compositor, so who cares??
So, in resume, wayland is not ready for nothing because it runs under Xorg to support not wayland software. Do you need xterm?? in wayland?? run it as xorg driver. If not you will have a pretty display and nothing else.
OpenPGP_0x57E64E0B7FC3BEDF.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
