OH NO NO NO WAYLAND SISTERS IT'S OVER!

> The frick you need color calibration for?
For my two monitors to look the same and have relatively correct colors.
> If you're looking for night light
No, I'm looking for color calibration, which is an essential part of any PC display server.
> KDE and sway both support this
Neither are what I use, perfect.
Wayland doesn't support it and last time I checked, their issue was still at "no way to properly solve it, let's shift it on the WM maintainers".
> You think dwl is an i3 clone?
I think that there is currently a single "mostly working" WM that is Sway and there is no BSPWM-alternative for me (there were 2 that died in the first year with most features missing, because Wayland
> You just mad you can't port over your x11 config?
No, I'm mad even Sway, which is the golden standard currently, didn't have proper acceleration and remapping/scrolling settings for my Trackball, making it unusable.

Color calibration is insecure. What if a compromised application changes your color settings?

It's supported by colord not wayland.

something as critical as a kernel needs to be open source anyway. You should be able to comprehend what you're building on top.

>your machine doesn't work
LMAO IQfy users are fricking morons

I am gainfully self employed and I made out like a bandit on several schemes. I own my own home free and clear and set my own schedule and activities. This year I am expanding my ginseng business to serve the ever hungrier Asian-American market.

Why do that when there's a perfectly good one already? But I don't even use Linux. I use OpenBSD.

X.org works fine here, not sure what your problem is, troon.

>X.org hasn't worked fine in 15 years.
Can you actually back this up in any way or are you just sore in the front hole, troon?

>pro wayland
>angry about /misc/
Many cases, sad!

I'm going to bump this thread every time you sage it.

wayland sissy gays trying to hypnotize normal human beings into using their shitting software lol

based

Honestly I can see the value in some of that stuff, but I agree that choice is no good when there's nothing that encompasses most of what you would want anyways. Feels like buying a FOSS smartphone where your choices are either you get the one that has a capacitive touchscreen or the one that has headphone output support, but you cannot get the one that has both, it's just not possible.

>holding it up to the bar of windows
I haven't been a Windows user in forever. Why bother?

Is that true? Windows is well known for always having had shitty buggy drivers.

X.org is old, therefore it doesn't count.

Again, they work at those refresh rates, but unless you disable vsync they're framerate capped. I'm using AMD too. This has been enough of an issue to include this:

https://www.phoronix.com/scan.php?page=news_item&px=X.Org-AsyncFlipSecondaries

Also 60hz VRR monitors -are- more niche. It's nice to have the option to not toss away one monitor because you might buy another one and it's honestly a lot more comfortable for multitasking.

It's very simple, I don't want to have tearing on the desktop, and I don't want to have my desktop capped to 60fps. X11 is one or the other.

Tearfree is tricky. Works with low latency, but has frameskipping issues. At high refresh rates it's not too noticeable, but still bothersome. It's never as smooth as what you would have if you use normal vsync on a single monitor with a high refresh rate on x11, or whatever wayland does.

Also besides KWin I don't know of any other compositor that's able to put a manual soft cap on framerate so that it doesn't jump to fricking 1600FPS or whatever and makes the GPU spike to full usage intermittently whenever there's something like an animation. Those animated drop down menus and such are a real riot. If your GPU doesn't have coil whine at such absurd refresh rates it might be fine, but personally I'm not a fan of letting this shit just run at a grossly unnecessary framerate. I'm fine with using KDE Plasma but I would love things to just work at least as well on the display side as they work on Windows. I've been using this workaround last year:

KWIN_X11_NO_SYNC_TO_VBLANK=1
KWIN_X11_REFRESH_RATE=165000
KWIN_X11_FORCE_SOFTWARE_VSYNC=1

on /etc/environment but it's a weird and imperfect way to get around this shit.

True. Unfortunately wayland managed to be even worse in the longrun.

Poettering has nothing to do with Wayland at all.

systemd does provide features that the alternatives don't have.

Yeah don't, it is honestly such a pain.

Have you tried playing with ForceCompositionPipeline? Vsync on or off? Compositor (try without)? export __GL_YIELD="usleep" helps? export __GL_SYNC_DISPLAY_DEVICE="$MONITOR" helps?

Why would I be foaming about some loser on IQfy who insists on harming herself by using dead software that she will never contribute to? Do you think you're special?

>Why would I be foaming about some loser on IQfy who insists on harming herself by using dead software that she will never contribute to?
Don't ask me why, I'm just stating the facts.

What is there to explain? You ARE absolutely mad that there is one person in the world running X11. I don't know how or why, but that's how things are.

And no one cares about your needs. Come back when you can address the needs of all other users with all other combinations of GPU, driver, kernel, monitors, resolutions, refresh rates, etc. Otherwise you're not qualified to comment on window systems. That's the scope of problem space, address it or get out.
Color calibration in X11 is a nasty hack that barely works, Wayland color management will actually work correctly but it's taking forever because this work should have been done by X11 people 25 years ago and they have to make up for all that lost time.

>X11 only "works" under very specific situations with very specific drivers and if you limit yourself to the happy path implemented by those drivers.
Wayland works in even more limited situations than X11 which is sad.

Only because of nvidia. Yes they are sad.

Most of the current blocking bugs are with the proprietary nvidia drivers.

Ah here it is, the typical wayshill playbook of "blame someone else for wayland's shortcomings".

Except that isn't happening. Wayland is developed by the same people as the successor to X11 and is forced to be compatible with X11 in a lot of ways so no matter which way you shake it, it's always the same people's fault.

> And no one cares about your needs.
X11 developers care, which is why it works.
> Come back when you can address the needs of all other users with all other combinations of GPU, driver, kernel, monitors, resolutions, refresh rates, etc.
It works with any of those on X11. Have been using it for decades.
> Otherwise you're not qualified to comment on window systems.
Lol.
> That's the scope of problem space, address it or get out.
It is already addressed by X11.
> Color calibration in X11 is a nasty hack that barely works,
Works properly. I simply load it with dispwin and it works perfectly.
> Wayland color management will actually work
Hahahaha. Maybe in another 10 years and every WM must implement it on their own.
> but it's taking forever because
As with everything Wayland devs seem unable to settle on any solution or say it's out of scope of the display server. Oh, sorry, "protocol".
> this work should have been done by X11 people 25 years ago and they have to make up for all that lost time.
Dispwin exists since at least 1996, when X11 was 12. Wayland is 13 already.

>X11 developers care
X11 developers are the same people as Wayland developers.
>It works with any of those on X11. Have been using it for decades.
You have tested every single piece of hardware in existence over the last several decades, with every possible use case? Proof?
>It is already addressed by X11.
Proof?
>I simply load it with dispwin and it works perfectly.
This does not work in various situations like if you have multiple monitors with different color profiles and an app doesn't support multiple monitors, or if you want an app to override the color profile. Again this only works if you stick to the happy path and only use dispwin, in all other situations it's broken. These issues are long known by people who actually use color management, it was never fixed in X11 because no one actually cares about fixing any long standing issues with X11.
>Maybe in another 10 years and every WM must implement it on their own.
In X11 it's even worse, every app must implement their own and even then it still doesn't work.
>As with everything Wayland devs seem unable to settle on any solution or say it's out of scope of the display server. Oh, sorry, "protocol".
There is one solution that's being worked on by everyone. That's another reason why it's taking so long, the more people the more time it takes to come to an agreement.

What is there to explain? You ARE absolutely mad that there is one person in the world running X11. I don't know how or why, but that's how things are.

Show the scientific proof. How are you measuring anger?

>Lie
No.
>Lie
No.
>Lie
No.
>you can get ICC profile information from xorg.
Which does nothing by itself, the app then has implement the color profile. There's no reason for that, it should be implemented by the server.
>And it will be ready in another 10 years.
You don't seem to understand, this will never be correctly implemented in X11 proper. 10 years is still better than infinity years.

>Proofs? There is nothing in issue tracker and the only mention I've seen is mailing list from 2019.
It got moved to gitlab later. Yes, they've been working on this protocol for 3 fricking years already lmao. Don't worry wayland bros, we'll get an hdr/color-management protocol one day. I'm sure it won't be totally gimped in some stupid way either if they ever do finish it.
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14

>All of the X11 developers are Wayland developers?
Most of them, not all.
>And, obviously, X11 devs care about this and Wayland devs don't.
Nope, they are mostly the same people who care about the same things.
>I have tested it on Nvidia, AMD, Intel with 1-5 displays with different refresh rates and WM/DE and so on.
Which displays? Which Nvidia, AMD, Intel GPUs? With which driver versions? Which WM/DEs? You need to be more specific. Anyway this is less than 0.000001% of the possible use cases. Now you need to test with every display ever manufactured, every GPU, every WM/DE, every app, etc. And I mean ALL of them. You can't skip ANY because someone who owns that will eventually cry and moan on IQfy that his shit doesn't work. Sound hard? Yes that's what it means to develop a window system.
>My system running right now with properly calibrated displays.
Not proof. No one cares about your system. You need to test every other possible system.
>I have multiple monitors from different manufacturers and use different profiles for each of them.
That's broken. You will witness that it's broken when you drag certain windows across the monitors.
>What? Any app can be put on multiple monitors in X11.
The app has to support changing the color profile or it won't work.
cont'd

Colord still works on wayland

>Colord still works on wayland
Example? I'd like to try it with a WM.

>Got anything to substantiate it?
Go look at the people who are actually leading development.
>Have a single example?
You can find countless examples in IQfy threads.
>there must be billions of such cases.
Yes, when you consider all drivers, displays, GPUs, etc. there are billions of combinations. You're finally getting it.
>ICC loading in X11 and dispwin in particular don't depend on your display type or sound card.
They do actually, display respond to gamma ramps in different ways, that's why you have to calibrate the display. Anyway that's beside the point, when developing a window system you have to respond to ANYTHING else that can break, not just the color profiles.
>Works perfectly.
You haven't tested it in all cases.
>Such as?
Anything that doesn't support color profiles in the exact way those monitors and that configuration expects it to.
>Are you moronic?
Please stop projecting.
>Color profile is not on per-app basis and doesn't require any support from them.
Actually it is and it does.
>If you say so.
I don't say so, cameras say so.
>Concrete example, please. Preferably with the settings that supposedly don't work.
Any video editor with any settings that don't match the display. Now it's obvious you're just a gamer troll and you don't know what a video editor or a camera is.
>They work?
No.
>So, calibrating displays is not a job for ICC profiles?
Correct, an ICC profile is just a description of some color ramps. You have to do certain things with them to calibrate the display correctly in all circumstances.
>Nah, you alluded at some vague "issues" at best.
Those are the issues, they're vague because X11 is also extremely vague when it comes to specifying what the color profiles are supposed to do or when they're supposed to apply. The situation is basically that apps can do whatever.

>Got it, no actual comparison list, but you are sure they are the most of X11 devs.
I'm not making a list of targets for you to go and harass, if you don't already know and work with these people regularly then you're just an outsider talking trash and it's pointless to talk about it with you.
>Suuure. It just happens that you can't give a single one.
I'm also not going to explain to you how to search a IQfy archive. You figure it out mister tech genius, you'll totally get it quickly with your 9 million IQ.
>Any examples of them being broken, though?
>Provide a case where it will be broken.
>No example?
Several were already given. You can't read.
>There you go pretending to be mentally challenged again.
Please stop projecting.
>Created from calibration hardware and software and applied to the screen.
The key piece is the calibration hardware and software, those are the most important part. Not the profiles.
>Nah, if there were any concrete issues, you would have been able to provide concrete examples.
Several were already given. You can't read.
>You can't.
Reminder you have nothing to add to this conversation besides "lol works on my machine"
>Works reliably on X11
Nope, try running an app that overrides dispwin, it will frick all your shit up.
>Hahaha, every time.
What's the problem here? Contrary to what you think, a window system cannot fix every problem with an extra protocol. Some problems need to be solved elswhere.
>Again, didn't you mention how Wayland will totally implement it correctly?
I wasn't going to say it because documents were already posted that explained it and assumed you could read. But since you can't, the way it will work is by having the compositor handle all color space conversions.
>By not doing it for the server?
This is doing it for the server.
>Seems like a regular Wayland "solution".
You don't know anything about window systems.
>Okay, you are mentally challenged.
Please stop projecting.

There are only two possible scenarios here.

Scenario 1: You don't know them and that's why you're asking me their names so you can go and troll and harass them.
Scenario 2: You do know them and you're just asking because you're trying to troll and harass ME.

Either way, I have no reason to give you their names. Make your tactics less obvious next time.

I'm not even the same person*

> There are only two possible scenarios here.
> Both are about trolling
As I said in

>you're asking me their names so you can go and troll and harass them.
Now I see why you use the word projection so much. Guilty conscience?

that's pretty sad.
Still, I want the lists because I hear this "They are the same devs!" from these threads (now I think it may be you samegayging in every Wayland thread) and never got any proof.
And it's always the same:
> 1. It's the same devs!
All the same devs?
> 2. Well, it's mostly the same devs!
Which in particular and how many?
> 3. I won't tell you which!

Also it's always fun how Wayland shills switch from "it's the same guys -> good!" to "X11 is a clusterfrick and was developed in moronic way".

from the way he's writing he's implying to be part of the development team.
he is either biased and spreading FUD about X11, or a larper.
either way, by engaging him you have allowed him to show it. thank you and keep up the good work.

of course there are no concrete examples. all the arguments wayland devs give for using it come from ignorance
after many egg-on-face moments they learn never to be specific, just like politicians

>I'm not part of any development team
Yeah that much is obvious.
>Anyone who actually worked on X11 over the last 20 years will tell you it sucks and needed to be replaced long ago.
maybe but wayland is not the answer

> You will never get it if you keep acting this way
> stop being a useless piece of shit troll
Okay, now I actually laughed out loud, thank you.

Absolutely seething, I will keep making Wayland threads as long as you're around.

If he isn't a Wayland developer himself (what does this even mean?) then it's just sad to watch.

>The Wayland solution makes full use of colord
What are we talking about here? Colord? No, it doesn't use any wayland-specific code or libraries at all. The proposed protocol? No, it doesn't use colord at all (obviously it wouldn't).

Colord manages display profiles. It can work on wayland because it doesn't actually use wayland at all but communicates via dbus.
>Wayland is not going to reimplement colord in a wayland protocol.
In other words, it will be gimped and garbage like I thought. Thanks for playing.

colord links to several X11 libraries and integrates will with xorg.
>It will be gimped and garbage because they don't pointlessly rewrite something that already exists and does the job correctly?
There is value in having a color management system that works correctly without relying on an outside daemon (dbus).

>Very little about color management actually needs a window system.
pants on head moronic.

To be fair, an HDR tty might be pretty cool? Should be possible in theory now I think.

>And I guess if I ask you to point to a single one of them, you'll go "search for them yourself", right?
No, in that case I will say I don't want to talk to trolls who can't follow the thread. Leave me alone and stop asking me to repeat myself. You get an F, you can't retake the class and you're expelled permanently.
>I can see that.
Observe 4 posts down where someone openly admits they want developers to get harassed

>The last time I posted names on IQfy they got trolled and harassed by people like you.
Good. Hopefully at some point they'll crack and either 41% or go work at Apple like they wish they already were.

> You will never get it if you keep acting this way
> stop being a useless piece of shit troll
Okay, now I actually laughed out loud, thank you.

Reminder you have nothing to offer these developers, actually you have less than nothing because you're a pest, your presence is destructive and harmful and time wasting to everyone involved.

>you can see the progress on shit like color management.
They've made 0 progress.
>The only step the window system needs to be involved in is applying the current profile.
There's more than that, but that alone is a pretty big step m8.

>They've made 0 progress.
Wow, that's exactly the same amount of progress you've made! You have so much in common with Wayland devs already.
>There's more than that, but that alone is a pretty big step m8.
No that's literally the only one that the NEEDS to be in the window system. Everything else can be outside, a few other things are more efficient when placed inside the window system and thus make the most sense to put there, but most things aren't.

Absolutely seething, I will keep making Wayland threads as long as you're around.

How about instead of keep making wayland threads you keep writing code and committing it? Oh right you won't because you can't.

They actually don't and that's how X11 does it. Obviously that way is bad and is easy to break so I guess you're not the same anon who was saying X11 does color management perfectly.

>X11 notifies clients of ICC profile changes so they can update correctly
This is just a hint that clients don't have to follow, it's not real color management.

Touch grass.

Can't, I live in the desert.

> works on my machine
> not a Waldi response to a bug
Wow, I guess all the closed issues with the reasoning “can’t reproduce” don’t exist then.

"Can't reproduce" is fundamentally different from "works on my machine". It can be reopened if you find a way to reproduce.

>These aren't useless people, these are people who actually develop the software we're talking about.
Unfortunately.
>That's not an option when trolls invade the IRC and issue tracker because it got posted on IQfy. Those are official communication channels used for the project, you can't "just close the tab bro".
Then ban them or temporarily lock the channel. It is not hard.
>Congratulations, if you really think this then you're the cancer killing FOSS, you're the reason why no sane person would ever contribute to it.
Wayland is the cancer killing FOSS.
Even Microsoft vendor lock-in hell is preferable to GNOME mentality being forced onto everyone. At least dwm.exe FRICKING WORKS!
>Every single instance of harassment I've ever seen in FOSS can be traced back to people like you on shit boards like this.
I see. I guess IQfy is a better board than I give it credit for.

>Then ban them or temporarily lock the channel. It is not hard.
It's not hard but it's tedious and annoying and a waste of time. Temporarily locking the channel hurts good users.
>Wayland is the cancer killing FOSS.
Haha what? Hilarious you say this when you spent the whole thread saying you'll never switch from X11, stay mad.
>Even Microsoft vendor lock-in hell is preferable to GNOME mentality being forced onto everyone.
What's a GNOME mentality and where did they force it on you? Did GNOME developers hold you at gunpoint and force you to install it?
>At least dwm.exe FRICKING WORKS!
Then go use it?
>I guess IQfy is a better board than I give it credit for.
Again you're openly admitting that you think harassing developers is good, and you still get butthurt at me for not posting the names of developers. Get fricked and die, c**t.

Not my job, I'm not a developer on this project.

>Yeah, well, shit happens. If you don't want janny work, put down the mop.
Or if you don't want to clean up shit then just don't invite shitposters to your project in the first place.
>at least it works
It does not.
>I regularly use tools like wmctrl that cannot be ported to Wayland by design.
By design wmctrl doesn't really work on X11 either. It requires the window manager to support certain atoms and some window managers break it.
>If they could, they probably would
So then they didn't force you.
>since most of them are apparently spics.
What's with the racism? This isn't /b/.
>I never need to worry about being harassed because I'm a goddamn adult that can accept criticism for my projects' shortcomings.
Schizos screeching racial slurs and conspiracy theories in your IRC channel is not "criticism of a project's shortcomings".
>People who cannot should be bullied out of FOSS. It is natural and right.
No and no. You're the cancer killing FOSS, you're the reason why competent people don't want to waste time with this trash. You're the reason why companies keep things closed source, they know a FOSS project with an open issue tracker will instantly get filled up with shitposts and bullying and will never be used to do productive work because the FOSS community is known to be trash full of schizos and beggars. Everything bad that you complain about is directly your fault and can be traced back to you. Get fricked and die.

>you can't even point to your own supposed concrete examples.
You missed your chance. You get an F, you can't retake the class and you're expelled permanently. Sorry better luck next time, don't be a useless sack of shit.
>Also, nice dodging a question of how come your supposed concrete example actually works on my machine.
This was explained about 20 times. "lol works on my machine" is not a valid response to a bug.
>For all I know it can be (you) trying to support your guilty narrative.
For all you know it could be your split personality doing it and you can't remember it because you were disassociated.
>It totally fixes you lack of any concrete examples.
You have already failed the class, examples will not help you.

> works on my machine
> not a Waldi response to a bug
Wow, I guess all the closed issues with the reasoning “can’t reproduce” don’t exist then.

>We're not going to coddle and apologize for useless people
These aren't useless people, these are people who actually develop the software we're talking about.
>They stop existing when you close the tab.
That's not an option when trolls invade the IRC and issue tracker because it got posted on IQfy. Those are official communication channels used for the project, you can't "just close the tab bro".
>If you lack the stomach to read mean words online, you should not be in FOSS
Congratulations, if you really think this then you're the cancer killing FOSS, you're the reason why no sane person would ever contribute to it.
>because even if you are not an incompetent homosexual, some schizo will inevitably do so at some point.
No they won't. It only happens when people intentionally invite schizos to your project by sharing the link to places that schizos populate, like this board for instance. Every single instance of harassment I've ever seen in FOSS can be traced back to people like you on shit boards like this.

>writing code and committing it?
Where? What project? What does "contributing to Wayland" even mean, in practical terms?

And most importantly, why should I?

Any project. Write your own window system, I don't care. Do something besides shitposting about things you know nothing about. The internet was a mistake.

What classes do you teach, and at which institution?

I teach potty training at the baby day care, you failed.

>These aren't useless people, these are people who actually develop the software we're talking about.
Unfortunately.
>That's not an option when trolls invade the IRC and issue tracker because it got posted on IQfy. Those are official communication channels used for the project, you can't "just close the tab bro".
Then ban them or temporarily lock the channel. It is not hard.
>Congratulations, if you really think this then you're the cancer killing FOSS, you're the reason why no sane person would ever contribute to it.
Wayland is the cancer killing FOSS.
Even Microsoft vendor lock-in hell is preferable to GNOME mentality being forced onto everyone. At least dwm.exe FRICKING WORKS!
>Every single instance of harassment I've ever seen in FOSS can be traced back to people like you on shit boards like this.
I see. I guess IQfy is a better board than I give it credit for.

>writing code and committing it?
Where? What project? What does "contributing to Wayland" even mean, in practical terms?

And most importantly, why should I?

>All of the X11 developers are Wayland developers?
Most of them, not all.
>And, obviously, X11 devs care about this and Wayland devs don't.
Nope, they are mostly the same people who care about the same things.
>I have tested it on Nvidia, AMD, Intel with 1-5 displays with different refresh rates and WM/DE and so on.
Which displays? Which Nvidia, AMD, Intel GPUs? With which driver versions? Which WM/DEs? You need to be more specific. Anyway this is less than 0.000001% of the possible use cases. Now you need to test with every display ever manufactured, every GPU, every WM/DE, every app, etc. And I mean ALL of them. You can't skip ANY because someone who owns that will eventually cry and moan on IQfy that his shit doesn't work. Sound hard? Yes that's what it means to develop a window system.
>My system running right now with properly calibrated displays.
Not proof. No one cares about your system. You need to test every other possible system.
>I have multiple monitors from different manufacturers and use different profiles for each of them.
That's broken. You will witness that it's broken when you drag certain windows across the monitors.
>What? Any app can be put on multiple monitors in X11.
The app has to support changing the color profile or it won't work.
cont'd

>I'd prefer nothing changing my color profile, that's the point of profiles.
No, this is the opposite of reality. When you work with image and video content the content has its own profile and that information is needed to display it correctly. You NEED to be able to change profiles on the fly. This is the main point of color management, not whatever the frick you're using it for.
>But give such an app and I'll check.
Any video editing app.
>there are other ICC loaders.
They all do the same thing as dispwin with the same shortcomings.
>It just works and it does its job perfectly.
Because you stick to the happy path on very specific hardware and the "job" you do with it is not actually a job for color management.
>Such as?
I listed multiple of them, re-read my post.
>Which issues?
I listed multiple of them, re-read my post.
>Proofs?
Proof is you. You won't even acknowledge the bugs exist because they don't happen with your specific hardware/software combination.
>Examples?
I listed multiple of them, re-read my post.
>Proofs? There is nothing in issue tracker and the only mention I've seen is mailing list from 2019.
See the MR somebody else posted and also these documents
https://gitlab.freedesktop.org/pq/color-and-hdr/-/blob/main/doc/design_goals.rst
https://gitlab.freedesktop.org/pq/color-and-hdr/-/blob/main/doc/winsys_color_pipeline.rst
https://gitlab.freedesktop.org/pq/color-and-hdr/-/blob/main/doc/winsys_hdr.rst
>Are you moronic?
Nope, that's literally how it works. There's a ton of writing on this subject https://en.wikipedia.org/wiki/Brooks%27s_law

>Proofs? There is nothing in issue tracker and the only mention I've seen is mailing list from 2019.
It got moved to gitlab later. Yes, they've been working on this protocol for 3 fricking years already lmao. Don't worry wayland bros, we'll get an hdr/color-management protocol one day. I'm sure it won't be totally gimped in some stupid way either if they ever do finish it.
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14

It's taking forever because they're making sure it won't be gimped.

> And no one cares about your needs.
X11 developers care, which is why it works.
> Come back when you can address the needs of all other users with all other combinations of GPU, driver, kernel, monitors, resolutions, refresh rates, etc.
It works with any of those on X11. Have been using it for decades.
> Otherwise you're not qualified to comment on window systems.
Lol.
> That's the scope of problem space, address it or get out.
It is already addressed by X11.
> Color calibration in X11 is a nasty hack that barely works,
Works properly. I simply load it with dispwin and it works perfectly.
> Wayland color management will actually work
Hahahaha. Maybe in another 10 years and every WM must implement it on their own.
> but it's taking forever because
As with everything Wayland devs seem unable to settle on any solution or say it's out of scope of the display server. Oh, sorry, "protocol".
> this work should have been done by X11 people 25 years ago and they have to make up for all that lost time.
Dispwin exists since at least 1996, when X11 was 12. Wayland is 13 already.