Linux Desktop Users Beg for HDR While Valve Gets Instant Compliance
Description
A four-panel meme about Linux gaming and corporate dynamics. Top-left: Tux (the Linux mascot penguin) on a green background pleading 'PLEAAAAAAAASE' with text 'I WANT HDR SUPPORT.' Top-right: A basketball player (LeBron James meme) wearing KDE and Wayland logos saying 'SHUT YO GOOFY ASS UP' and 'CRAKKKA ASS THINKS HE CAN TELL ME WHAT TO DO.' Bottom-left: Gabe Newell (Valve CEO) looking concerned with text 'WE WANT HDR ON STEAM DECK.' Bottom-right: The same basketball player now subservient saying 'YES SIR' and 'GLORY TO THE VALVE coporation' with KDE and Red Hat logos. The meme satirizes how Linux desktop environment developers ignore community requests but immediately comply when Valve (a major corporate backer) makes the same demands
Comments
35Comment deleted
Linux desktop: where your feature request stays open for 8 years until a corporation files the same ticket with a check attached
The open-source feature request pipeline has two priority lanes: 'community_backlog' for users, which is a symlink to /dev/null, and 'corporate_mandate' for Valve, which triggers a pull request before the email is even finished sending
the problem is Game Mode doesn't use KDE nor most of Wayland Comment deleted
No wonder Comment deleted
How come Comment deleted
An entirely separate Wayland session with it's own compositor, KDE is baked in as default "desktop" mode SteamOS user could switch to Comment deleted
grok what is "funding"? jarvis, look up "cost of development" for me. siri, please tell me what "features take time and effort to implement" means Comment deleted
like istg some people really think all a dev has to do to enable HDR support is write supportsHDR=true Comment deleted
actual question in case of Wayland, it's been 17 years in development ffs Comment deleted
"in development" - for most of that time it was mainly figuring out how to tackle the wayland standard on an abstract scale. Comment deleted
making standards isn't just "I've decided it's going to be like this" especially when it's something as important to get right as the replacement for X11 Comment deleted
it's not that hard to improve upon X11 unless you don't mind shooting your legs out from the get-go, which is the case Comment deleted
idk fam, the Xlibre project has become a laughing stock these recent months for trying Comment deleted
Sounds like what Matrix says when it takes them 6 years to implement captions for photos :( Comment deleted
I bet it could legally drink sooner than achieve base goals so it will be over and time to make X13 Comment deleted
wayland is literally just X12 all the devs that worked on X11 are now working on wayland because X11 has become unmaintainable and structurally unsound the entire point of taking so long to decide on good standards is to not have to do a full-scale replacement like this again Comment deleted
IIRC there are parts of X11 that no human being understands completely and authors are long gone Comment deleted
that's bound to happen in any large project Comment deleted
but afaik some X devs left precisely because it had become so unmaintainable Comment deleted
part of the problem is there are "vritual" devs who clearly don't work on Wayland and can't say why the heck their code was written in the specific manner and Wayland architects were bound to fail in these cases Comment deleted
what's that even supposed to mean Comment deleted
A number of features that were implemented in X11 and were in scope of Wayland weren't considered a thing by the standard makers and had to be added in the feature list after with full reimplementation without knowledge of edge cases. It made a lot of legs hurt in the process. Comment deleted
X11 and W have completely different code structures, I don't think you could migrate most features even if you tried. and the W standard gained features one-by-one based on how important they are. HDR is just not very important, so they did that part later than most of the other stuff Comment deleted
DRI stuff has some similarities (ironic), but not in structure. Comment deleted
Errors, Oversights and Omissions This section attempts to document the failings of the X protocol and rendering model. Learn from history, or be doomed to repeat it. Infeasible to change color depth with clients running Possibly not worth fixing. https://www.x.org/wiki/Development/X12/ love that funny wall of text Comment deleted
…wayland can do that afaik. at least sway lets me do it, kinda Comment deleted
sway supports rendering in higher bit depths but it's not quite HDR, and it has some bugs Comment deleted
KWin can do that. With full reset XD Comment deleted
oh wow last updated in 2017 🤭 that's just after most people agreed for wayland to become the X successor Comment deleted
a true time capsule Comment deleted
I don't think that sentence has changed since 2008 but we can check Comment deleted
lmao Comment deleted
yeah it's that old Comment deleted
geez Comment deleted
is it "political coordinates" kind of meme? Comment deleted