GNOME's Mutter Sees More Cleaning That Ultimately Could Help Foster Vulkan Support

[pal666]

Yeah, why should anyone listen to what users want?

paying users?

[DanL]

If it’s not needed by GNOME then it won’t happen for now.

You were already told (by an X release manager no less) that this is a bunch of BS: https://www.phoronix.com/forums/foru...71#post1141771
Conveniently, you didn't respond, and here you are repeating the same trolling/nonsense...

Don’t like this fact?

Pfft. Your "facts" are mostly things you fantasize about.

[DanL]

to please Nvidia users?

Yes, because Nvidia users are clearly the only ones that benefit from Xserver fixes...
3/10 on that trolling. If you want to really learn how to do it, study 144.

[DanL]

"We will keep an eye on it as we will want to ensure X.org stays supportable until the end of the RHEL8 lifecycle at a minimum"

LOL. That is several years from now. I've pointed that out to you in the past. (But as usual, you never learn). Also, RH devs ideally want a regular release cycle. I've pointed that out to you in the past. (But as usual, you never learn).
Are you sensing a theme here?

Oh and guess what, half of the MRs tagged for 1.20.9 are Xwayland related.

And half of them aren't. If you're trying to make the point that X development is limited to XWayland, you just failed and contradicted yourself.

Matt Turner is now a X Release Manager? Biggest laugh ever.

No, the biggest laugh ever was when you tried to convince us that releasing Xserver 1.20.6 was purely GNOME-driven and Matt called it an "amazingly stupid argument". And you had nothing to counter with because you were talking out your ass (as usual).

[DanL]

So it’s Xwayland until EOL.

It's too late. You already acknowledged that there's more to XServer than XWayland commits. That's why it's fun toying with you. The more you type and reply, the more likely you are to say something stupid to try to support your fantasies.

[DanL]

Bye

If only you really meant that.

[dkasak]

There is no such setup for which it "just works". If you don't see anything wrong, it's because you don't know where to look at. On Xorg, however, the issues are less prominent as the current generation of Mutter was specifically designed to be optimal on Xorg, and most of the bottlenecks are in the code that hacks this Xorg-targeting release to work on Wayland.

It seems like you didn't/couldn't give a straight answer to my question. Can you guess if I'm shocked?