Thread 106359648

In 2032, wayland will be as old as X was when development started
do you think by then it will be a good replacement for X?

>>106359648 (OP)
>do you think by then it will be a good replacement for X?
No.

nope, internal tranny drama won't let it be as mature

>>106359648 (OP)
just two more decades and it will be usable

>>106359648 (OP)
It can never be a good replacement for X (or anything else) because of a difference in policy. Certain things will never be possible because the devs dont want to allow it.

>>106360570
This, I will never use it for this reason.

It's alright today, Ive used it daily for 2 years now.
If gnome devs weren't such stonewalling cunts, it might even have 1:1 feature parity with x11.

>>106359648 (OP)
All wayland compositors will be written in rust by then...

>>106359648 (OP)
I'm using wayland now, it's pretty decent. What issues do you have?

>>106360570
what specifically are they blocking, out of curiosity? i've used both recently and do some pretty unusual stuff (like GPU passthrough and kvm frame relay) and both seem to just werk.

>>106359648 (OP)
Nope, not a chance.

>>106359648 (OP)
If you look through the code of wayland, it’s pretty clear they are just doing the equivalent of pushing papers around.

Like, to fix the core wayland message passing from going into a busy-wait loop when you give it a 4097 byte message (Secure, eh?) they simply hard-coded the message size making the dynamic message size code essentially dead because they really didn’t know what else to do, and for this one line diff they produced novels of text to make it look like they were doing something.

It’s going to be a whole new attack surface so eveyone with a wayland app thatcan get on your machine can have their own built-in “Recall” like features.