The Wine Wayland driver has now merged pointer warp support

[-]

felipec@reddit

So there's a chance wayland will be actually usable in 2040.

[-]

felipec@reddit

Delusional. Delete Xwayland and let's see how well Steam runs.

[-]

loozerr@reddit

The benchmark of of a computer is usable: does steam run

[-]

felipec@reddit

Xwayland is X11.

Newer generations of linux users are so illiterate when it comes to linux that you don't understand the difference between X11 and Xorg. That's why you blindly believe all the wayland myths.

[-]

loozerr@reddit

Yes, go ahead and run multi monitor vrr while gaming with pure X and come back and tell how wayland + xwayland "is X11"

[-]

felipec@reddit

Yes, go ahead and run multi monitor vrr while gaming with pure X

I have absolutely no problem doing that.

That's just one of the many myths wayland propagandists spread.

Thanks for proving my point.

[-]

loozerr@reddit

Imagine being so opposed to change that a genuine improvement is "propaganda"

[-]

cupkaxx@reddit

I am so glad whining doomers like you aren't maintaining these awesome projects

[-]

FeepingCreature@reddit

Pretty close now to a actually_x11_had_reasons_for_having_the_capabilities_it_did_so_were_just_adding_them_back_with_a_groveling_apology_v3

[-]

Nope, this is still better because the warp position is bounded by the surface/window. Unlike on X11 where any misbehaving application could set mouse position to anywhere (maybe even another monitor).

[-]

somethingrelevant@reddit

the pattern does kind of hold though. wayland says "no we're not adding that, it's outside the scope or insecure" for years, then ends up adding it because it turns out people expect their computer to work properly and don't want a compositor that doesn't let them turn off vsync or use push to talk globally or have scripted window positioning or mouse warping or

[-]

FeepingCreature@reddit

Eh, they'll add that too.

[-]

EmptyVolition242@reddit

Lmao

[-]

ShimmerFairy@reddit

This was always the inevitable endpoint of Wayland really: all the same features X11 has, just shuffled around and spread out across multiple standards-keepers. The original design of Wayland is just too locked down and simplistic to meet a lot of real-world needs.

[-]

Misicks0349@reddit

eh IDK, sure there are replacements for certain things like (in this case) pointer warping, but they do often differ on the implementation level and often the usage details. Input Method handling for example is different on the protocol level to x11 even if it "feels" very similar to use (though, of course with less cruft like GTK_IM_MODULE and QT_IM_MODULE unless you need to use IME's with Xwayland apps). There are things that will never have a direct analog of course, wayland is never going to become network transparent in the same way x11 is, and things like global positioning are things that compositor implementers don't seem too keen on (not just GNOME).

Wayland is just too locked down and simplistic to meet a lot of real-world needs.

Intentionally so of course, its very simplistic because the core wayland protocol is supposed to be the bare minimum require so graphical clients can display on your machine. The protocol system isn't a bug, its a feature. Its very similar to web standards actually.

multiple standards-keepers

I'm not sure what you mean by standards-keepers, do you just mean different compositors?, there is only one wayland protocol standard and its hosted on freedesktop.

[-]

JaZoray@reddit

why

[-]

MarkSuckerZerg@reddit

When the copy-fails CVEs hit, we had people arguing, quite convincingly, that for a desktop user, there is no point in privilege escalation. Everything interesting that can be exfiltered or ransomed is already in /home with full access to all user's processes. Rogue program has access to .bashrc where it can set alias for sudo.

So we have this desktop environment with fully open filesystem access, but GUI that treats everything as a malware with no or obscure ways to opt-out.

[-]

kansetsupanikku@reddit

explain? it's X11 where it was trivial and possible to miss, and Wayland where any virtual input needs to be explicitly allowed

[-]

JaZoray@reddit

if wayland is supposed to be a replacement, it needs to be better

[-]

kansetsupanikku@reddit

You've literally named a scope where it is

Better universally, though? I don't see that ever happening. regressions in terms of niche, professional, and accessibility features were always a shameful thing that was happening, and transition to Wayland hits many such uses hard. And the business behind it doesn't care.

So I don't see X11 setups becoming entirely unavailable in 10-15 years, even if all the mainline distributions drop it. And removing it from certain pieces of software is not going to be a flex some people make it seem to be.

[-]