@dysfun Sorry, I thought you had some tangible features in mind where people have spent effort, but do not benefit also the desktop. E.g. some protocol extension. I cannot think of a single protocol that isn't somehow relevant for some desktop.
@dysfun I think the protocol modularity is good for the desktop in the long run. Problems and use cases can be solved one at a time, and they can be iterated on. Solving everything at once would take even longer, or the result would be just another copy of what already exists without any clear way to try something new.
@BrodieOnLinux FWIW I firmly believe that snarkyness, sarcasm, and ridicule will only cause unnecessary negativity. They rally people to have "fun" by punching down the target. They are powerful tools of destruction, that create a mob.
Luckily I haven't read posts that target me in a long time, but I can assure you, the emotions the comments trigger in me are hatred, sadness, frustration and demotivation.
@jon_valdes
@demofox I wonder what data types you/they used there and for what kind of data, to cause all that need for dithering? Optical vs. electrical, primaries, dynamic range...
@jon_valdes Oh, don't worry. I always wonder if there is some insight I haven't realized yet.
I have indeed been doubting if 10 bpc is even enough for electrical BT.2100/PQ, and I've been hoping that 16-bit floating-point would be enough for optical display-referred data.
Very long and slow gradients is a good point to make. Without dithering we would need the stimulus change from one code value to the next to be imperceptible when laid out as two flat fields side-by-side.