@mcc Khronos discussions are basically *a lot* of conference calls and occasional face to face meetings, a lot of "voting" and tracking "who can vote" based on attendance, and a lot of writing proposals in weird dialect of English that is "spec language". Who wants to do that, and who has time to do that?
One possible, I'm sure hypothetical scenario: someone who's not terribly busy working on the engine itself. Heck, maybe if they spent their time on calls they'd cause less damage to the code!
@mcc (this is 900% exaggerated, but there's a grain of truth)
And so you *can* end up in a situation where company's representatives on Khronos do not *necessarily* voice company's opinions or wishes. They are just *there*, saying whatever they want to say; they aren't quite aware of what the engine needs or wants, and vice versa the engine is not quite aware of what they are saying. A gross oversight from "management" I guess.