|
|
|
|
|
|
by shevy-java
35 days ago
|
|
|
> that is what the X developers did with Wayland This is rather incomplete. For instance, gtk devs already threw out tons of old code in GTK4. Wayland also has fewer features than xorg; and there are also fewer choices available. I noticed this with regards to WMs/DEs. I am not even going to issues wayland has with regards to certain video graphics - that's another not mentioned issue here. You are trying to pick individual cherries. > This sort of thing is why to fix X11 security you have to give up backwards compatibility and create a new X version. I don't think so: https://github.com/X11Libre/xserver Let's have a look in a little while. I myself hope for better and more transparent information at all times. Probably others want better security overall. Would it not be somewhat interesting if wayland were to be abandoned eventually due to having too few useful features compared to xserver? |
|
|
Because Wayland is a strictly a window management protocol focused on policy over mechanism.
> I am not even going to issues wayland has with regards to certain video graphics - that's another not mentioned issue here.
We also aren't going to mention issues Xorg or XLibre have with some graphics setups, because that's neither here nor there. This is a thread about security.
> I don't think so: <XLibre github repo link>
Didn't XLibre break some applications when launched?
> Would it not be somewhat interesting if wayland were to be abandoned eventually due to having too few useful features compared to xserver?
It would be interesting to see Wayland abandoned for a better protocol/set of protocols, xserver is neither a protocol nor really better.