HackerTrans
TopNewTrendsCommentsPastAskShowJobs

throwaway7489

no profile record

Submissions

Gnome Mutter Now "Completely Drops the Whole X11 Back End"

phoronix.com
40 points·by throwaway7489·8 เดือนที่ผ่านมา·72 comments

comments

throwaway7489
·8 เดือนที่ผ่านมา·discuss
I apologize for my previous misleading comments. You're right, Wayland causes many problems. As a long time Linux user, I miss how capable X was and don't want to see it go. Wayland compositors feel like toys in comparison, and its advocates sometimes seem to be coping. However, with major DEs and toolkits dropping X11 support, what options do we truly have?
throwaway7489
·8 เดือนที่ผ่านมา·discuss
Those are not lies. I don't think you know what you are talking about. If you knew, you would know that waypipe + xwayland-satellite works even for forwarding X11 clients over waypipe. I use it myself every day, but it's pointless to discuss it with someone who isn't interested in listening, only in spreading the same lies as everyone else.
throwaway7489
·8 เดือนที่ผ่านมา·discuss
Wayland gives us a lot. What you don't realize is that Wayland _is_ X12.
throwaway7489
·8 เดือนที่ผ่านมา·discuss
> What is that?

I believe they refer to KeePassXC's autofill feature, which autotypes credentials into other applications. I've never used this in X and won't use it on Wayland, as I prefer to keep all applications isolated.

I Ctrl-C to copy and then manually paste the password. Wayland is better for this method because I know the clipboard is cleared once I close KeePassXC.
throwaway7489
·8 เดือนที่ผ่านมา·discuss
Thanks for pointing that out. I just learned about the policy, my bad.
throwaway7489
·8 เดือนที่ผ่านมา·discuss
It's not misinformation, that's how X still works. Clients do all kinds of things. New programs aren't like 80s ones but your X server still must support every operation clients expect.

Wayland doesn't break anything, it's a completely new protocol. Claiming Wayland breaks your use case is like saying systemd broke old init scripts. It did because it's a different system.

Wayland isn't trying to be Xorg 2. It's a protocol. At its core it's only a compositor protocol. Everything built on top is up to the implementation developers.
throwaway7489
·8 เดือนที่ผ่านมา·discuss
Posting from another account.

I'm aware that extensions exist now, like present, which make it possible to send buffers, similar to how Wayland operates, so you don't have to do things the primitive way.

However, to claim to speak the X protocol, you still need to support the older functionality, that's what I mean by a tremendous amount of functionality to support. The moment you get rid of that old functionality, you've essentially created a new protocol, which is what Wayland is.

How is that point nonsense? I don't want to see X go, but I don't think it's reasonable to prevent progress.