Fake. The “gaming issues” was the lack of direct scan-out, which for most people who gamed with v-sync enabled anyway changed nothing, I’m speaking in the past tense because Wayland has had direct scan-out for years, and it did not require a complete re-write of anything, it only required a new extension, which you can do when your protocol is based on extensions. You know what’s even better than direct scan-out? Vrr, which you can have while using multiple monitors each with its own refresh rate, and with the future frame timing protocol the experience will be even better

Also, “in my experience” means nothing. In my experience gaming on Wayland is perfectly fine, and my experience is worth the same as yours

At least mutter and kwin both handle multiple monitors and vrr perfectly, I’m sure other compositors do as well. And by handle I mean actually treat them like two displays, not “we make a single virtual display and output it on two ports while pretending all monitors have the same refresh rate” like it is on xorg

And what is the technical merit in question? “Everything we didn’t change works the same”?

Daaaamn, good thing that the main selling point was “everything you used before works the same”. I guess it does not have feature parity with xorg, huh?

Oh, oh, I just noticed another inconsistency without even trying. You know all the babble about hardware support scattered throughout this and most anti Wayland posts, that it’s mostly about nvidia? Well guess what? Xorg has literally worse nvidia support! That’s right, X11 works on Nvidia only because the proprietary Nvidia drivers ship with an Nvidia specific implementation of the xorg server, but if you were to run real Xorg and not Nvidia xorg, it would have the same problem you have on xwayland. Except that with xwayland you get all the compatibility benefits of the recent move explicit sync in Wayland, that you would miss on plain xorg, so you would get all kinds of synchronization issues.

You need to understand that Xorg is not a good piece of software by itself. Its entire value is staying unchanged and not having breaking changes. Once you remove that it becomes unuseful. On top of that, meetux did not introduce “breaking changes” in the sense of “new features that changes the API” he introduced “errors that slipped review” because he is not good enough to write code for Xorg. What did he say, that he is anti-dei and, and we should only include people based on skills? Well then he should be glad that he was excluded because on top of being an asshole he also lacks skills.

Wow, that wall of text you linked sure is worthless. First of all, you can’t even tell if it’s signed by three different people or a single arrogant one, either way just sad, and in any case it’s only one sysadmin. But you can just scroll to random points without reading and find contradictions.

For example, I scrolled and found the governance part, it says on X11 there’s standardized protocol and changes go through a democratic review process, but the same is true for Wayland, the people who develop Wayland are the same who developed X11, and Wayland is heavily standardized, but the protocol is subdivided in extensions of which many are optional. Then it goes on saying that by contrast on Wayland you have a dictatorship of compositors because each can implement parts of the protocol as they see fit, but this doesn’t make sense because if anything having a single server that decides everything is a dictatorship, while allowing desktops to decide what to support is democracy.

I won’t waste time reading all that, but I’m sure it’s like this throughout.

Also, the IT guy from your local high school is probably a sysadmin managing 500+ computers. It’s not a particularly qualifying position.

why I use xlibre…

Because you are delusional. Next question?

Just remember that this is the kind of code quality of xlibre, the guy doesn’t even know C operators and is trying to write a fucking display server:

Meetux was banned after breaking the xserver multiple times, and then acting like everyone was conspirating against him about it.

You say this like there’s any chance of it not failing

Well, then I’d say that’s a bug report alright

You will not be limited, as long as you enabled 165hz in the settings. Tho, you might experience some minor latency, at most one frame, but you really shouldn’t, it depends. I would say that at 165hz, one frame of latency is not that much.

Also the compositor tearing option is there to allow the game to skip v-syncing and cause tearing. But, if the compositor allows tearing, and the game implements vsync, it will not tear. Actually, having both vsync in the game and tearing disabled in the compositor could cause more latency, but it depends, it might not.

Edit: I first said you should try what other comments said, but then I saw you already replied to them

Also, you said you are willing to lose some FPS by compositing the game to have windows on top. I want to make clear that you cannot have windows on top of the game without compositing. This is not a Linux/KDE/Wayland thing, it’s just that compositing is the process that draws the windows. If this were an XBOX, so running a gaming-specific version of Windows on custom gaming specific hardware, it would still need to do compositing to draw a window on top of the game. Only something fullscreen can skip compositing, because at that point there’s only one window to draw without any positioning or shading necessary. But compositing is done per display, so you could put those windows in a second monitor and still skip compositing the game.

Out of my ass I would say that this has to do with kde trying to optimize the full screen window by skipping compositing for it (direct scan-out, useful for e.g. gaming), of course this is not possible to do with windows on top (they have to be composited). I would have expected KDE to disable direct scan-out once you put windows on top, but maybe it doesn’t.

I recommend posting this to KDE’s bugzilla, they should get in touch pretty quickly for something like this, of course recognizing and solving the issue are two entirely different things.

But before posting, I’d suggest you do a test: you can disable direct scan-out globally by going on “display settings” and unchecking “screen tearing: allow in fullscreen windows”. Try and see if the issue goes away. And make sure to mention this test and the result on the bugzilla post.

I’ve been using it on my Amazon firetv stick, and I’m loving it. I first tried it because I cannot use revanced on the fire stick, but it’s actually pretty good.

Also, you can link it to your official YouTube app and control it from your phone

First of all, they were developed around the same time; second, no one said that a protocol should remain unchanged for 35 years. And lastly, the people in “what’s wrong with these people” are the people pretending gopher is any good today, and a reasonable alternative to the web, which factually isn’t the case as apparently it did remain unchanged for 35 years. And if it didn’t remain unchanged but did not add certificates, it would just make things look even worse.

Wait, gopher didn’t use certificates? What’s wrong with these people? And of course these are going to be just gpg certificates, not authoritative I imagine, or it would defeat the entire decentralised thing.

I really don’t get this stuff. If you want pure text websites, just make them, you are allowed to use pure html, you don’t have to use JavaScript if you don’t want to. You can get real certificates for free from Let’s Encrypt, and you can use any free DNS service you want

Is this just yet another gopher protocol? Or does it come with anything interesting

Wait a bit for the new steam controller

my cheap ass salvaged speakers. I got them from a friend who got them from her father who got them from a school janitor who got them from a school that was throwing them out. Each of those step did some “repair”, until they got to me and my roommate, and we undid every previous “repair”. we are still using them

You 👆

You can still plug a controller with AA in and use it while the batteries are in the charger