I think that the lack of Oklab is actually a mild but significant Accessibility issue.
There is a range of physical imperfections in cones in the eye and neurological conditions that impede a person’s ability to see colour and process it. Engaging with a program when colour does not behave as it should would affect those more severely and is a barrier to use. And any work a-rounds used in real life spaces would be harder to implement.
I’m not familiar with the code base but it sounds like it’s more than just optimizations needed, and could even be potentially complete rewrites.
If Krita is to implement it, sounds like a step-by-step plan is needed to tackle it and it might be a major release. In that case, would a specialised fundraiser help?
@rkspsm also thank you for your work, and you too @urzeye
I have found a video that I believe that explains the designer’s frustration a bit more with using the RGB HSL colour space. I’ve taken a sample out for passing readers to understand how much it would help ease of use.
In particular in the talk, Anton creates a drop in example using an okLCH colour space converter vs a HSL that shows that if you were to automate, how you would speed up designing. It’s very impressive and it’s around the end mark at 29:25 here:
