SDL2 Reverts Its Wayland Preference - Goes Back To X11 Default
Collapse
X
-
Originally posted by birdie View Post
Countless people discussed that content with you for the past months, and how most of it doesn't make sense from a Display protocol's perspective. At this point I'm convinced you're just being a troll and a spammer.
Comment
-
-
Originally posted by Vermilion View PostBug report:amdvlk+Wayland: good
Comment
-
-
Originally posted by birdie View Post
Originally posted by RealNC View PostIt's a wayland problem in the sense that if you use wayland, you'll get that issue. The blame game is not really relevant. If you get more input lag in wayland, then who's fault it is doesn't fix the issue that you get more lag in wayland.
Originally posted by RealNC View PostThe end result is the same. Doesn't matter who's fault it is, really. Mesa has some issues, nvidia's blob has even more issues, so using wayland has issues and hurts adoption.
Comment
-
-
Originally posted by RealNC View PostIt's a wayland problem in the sense that if you use wayland, you'll get that issue. The blame game is not really relevant. If you get more input lag in wayland, then who's fault it is doesn't fix the issue that you get more lag in wayland.
Originally posted by RealNC View PostThe end result is the same. Doesn't matter who's fault it is, really. Mesa has some issues, nvidia's blob has even more issues, so using wayland has issues and hurts adoption.
Plus while the problem is being made out to look worse than it is by leaving out information. For example..
Originally posted by RealNC View PostThe issue is that retroarch tries to reduce latency. Other games or game-like just use whatever they're given, in this case 4 swapchain images. In retroarch you can configure the swapchain size. But it doesn't work in this case. Even if you set it to 2, you get 4.
So by saying "X at least allows you to disable compositing to get less latency" when comparing it to Wayland, it can be read with an invisible "than Wayland" appended to the end. In truth, the only thing you can universally append at the end of that is "than it gets with compositing enabled".
Comment
-
-
Originally posted by Weasel View PostWhy does it matter if he codes? Design decisions that matter if you code are those internal to a project, not to an end user. If a design decision impacts end user then nobody gives a shit if he can code or not.
He believes, for example, that Wayland should have protocols built into it that enable a client to access the buffers of other clients and the compositor even though Wayland clients already have ways of doing that. Clients can do both of those things and more with Pipewire and it's done in a way that work for both Wayland and X11 sessions.
An end user would get the same result whether or not capture is done via Pipewire or via a Wayland or X11 extension, but birdie's pissed that it's not part of Wayland.
He's also argued that a shared object isn't actually a shared object if only one thing decides to use it. Dude just doesn't know what he's talking about.
Originally posted by Weasel View PostIn fact that's probably the issue here, since Wayland developers (those who develop the protocol I mean) are a bunch of retards who thinks the world revolves around their computing needs and reject any sensible feature request that other users want out of their display server/protocol because they use it on X11.
Claiming "it's not needed" makes them a bunch of lunatic fringe fucks.
Originally posted by Weasel View PostClaiming "it's not needed" makes them a bunch of lunatic fringe fucks.
Comment
-
-
Originally posted by Vermilion View Post
Was wondering how come the title mentioned Wayland yet you didn't link your issue sooner. Guess I needed more patience.
Countless people discussed that content with you for the past months, and how most of it doesn't make sense from a Display protocol's perspective. At this point I'm convinced you're just being a troll and a spammer.
So please kindly never mention me again and never reply to my posts, OK?
Comment
-
-
Originally posted by Myownfriend View PostThe reason why Gnome night light doesn't work on Nvidia hardware in Wayland is because the driver doesn't support GAMMA_LUT
Comment
-
-
Originally posted by birdie View PostSo please kindly never mention us again and never reply to our posts, OK?
I agree on many of your points, but your extremely toxic and aggressive attitude doesn't help.Last edited by tildearrow; 19 April 2022, 04:48 PM.
Comment
-
-
Originally posted by birdie View Post
Countless things (for a start X11 has a single server, for Wayland we now have what? two dozens?)
I'm not sure that Wayland has anywhere near two dozen compositors but maybe I'm mistaken.
You should really watch Keith Packard's A Political History of X.
Originally posted by birdie View Post...prove that whatever developers have on their minds is as remote from being rational and sensical as possible.
If requiring common sense and much needed common API is trolling, then something might be wrong with someone's grey matter.
Originally posted by birdie View PostSo please kindly never mention me again and never reply to my posts, OK?
Comment
-
Comment