[thomasfl]

I worked for the Norwegian standard organization at the time. After seing with my own eyes how Microsoft was able to get OOXML approved, I quit doing standards. The OOXML standard is a joke. Three different ways to store basically the exact same thing. Like dates.

[sevensor]

Indeed. “The bad standard is the result of negligence rather than malice” is a total nonsequitur. It in no way excuses pushing a bad standard on everybody to say, “they didn’t mean to make it bad.” It was still bad in obvious ways, and they still did power moves and underhanded things to get it signed off over legitimate technical objections. The reasons it was bad are irrelevant to the fact that it was bad and they promoted it.

[itsthecourier]

wow. thanks for sharing

[fsflover]

What if they could do it, because people like you had quit?

[izacus]

Standards committees being completely divorced from reality of software engineering is why most of the standards are useless.

So the question is whether it was actually a loss.

[perching_aix]

What if then? Should they have just bodied the thing for the love of the game? So that people uncaring for their wellbeing then wouldn't have appreciated it as a sacrifice anyhow?

Quite often I find that if people stopped holding fundamentally broken dynamics together and just let the thing fail and fail hard, the overall long term outcome would be better off. Much to the opposite of your suggestion.

It's just that turns out, things being properly bodied or properly broken take coordinated action. People deciding one by one, one way or the other, is what actually enables and sustains pathological dynamics like this.

But then how does one single out any specific decision? Well, nohow, not with any rigor for sure.

[thomasfl]

I was new in the standards business. Believed this was common. Understand now that it wasn't.