> It's a bit sad that the author went to the depths of buying this domain, create this page and then don't provide a correct library they think it's appropriate like https://colorjs.io/
Colorjs.io doesn't address most problems the website highlights.
And when there's no way, you use libraries. Others also mentioned CSS4 solutions and other alternatives. It's really not that bad as the articles paints it (pun intended).
A) someone needing to change image processing behavior on a browser isn’t impossible, is just not possible with a JavaScript library. Lots of different kinds of developers here. B) How workable the current situation is depends on your use case.
I imagine his exactly the sort of thing the author was hoping would be improved. But the existence of an experimental, largely unsupported API doesn’t really solve the problem though, does it?
Listen — I’m not really sure what your problem is and I don’t really care. I have no interest in “winning” a conversation. If you’re just going to push goal posts in different directions to try and find some way you feel righter than me despite my having done nothing besides making several specific, one-sentence, topical points, then I yield the remainder of my time for you to go ahead and do that by yourself.
Colorjs.io doesn't address most problems the website highlights.