So much of X was built on bad one time hacks that never died, that ossified into place. It's zero surprise to me that Wayland folks didn't rapidly promote the

So much of X was built on bad one time hacks that never died, that ossified into place. It's zero surprise to me that Wayland folks didn't rapidly promote the first pass at color management to official status. Headlines like this are misleading as fuck. It elevates the consternation of those wondering "why wasn't this here already?!". But this is the hopeful 1.0 of a long road, of compositor specific tries, of countless iterations & tweaks. The case for respecting a long hard process are vastly vastly vastly undersold. Short un-understanding quickly dominates. It's easy to say why wasn't something there? But in 20 years, it would be way worse and way harder to say "why was such a bad thing approved?". It just takes a lot of time, for incredibly open ended problems to find reasonably good satisfactory resolution, that multiple implementers will feel is a good sound protocol to work from. It isn't a desire for minimalism that drove Wayland protocols, it's a shock horror & critical terror at what the sloppy past had allowed to grow up & a recognition that what gets 1.0'ed needs to face a much higher standard than what happened in the past, needs a far higher level fo confidence & future sightedness. Don't ship slop. Appease the user of now, or build an enduring legacy that can keep building: the early-game people will forever protest & scream about how bad the late-game builds are at doing the thing, but the late game people almost never ever get the respect & accolades for ascertaining & achieving the true long term objectives. But if they weren't there, there's such a real chance the whole enterprise might have fallen over & collapsed.