I agree in principle; a reasonable spec that doesn't change all the time is what's needed for supporting next-gen browser development (as in inspire a new generation). But that's not what's happening at all; collaborators of github.com/whatwg even welcomed the rejection of HTML profiles/subsets and target device classes when the idea was brought up by MS (to save IE, but still ;)
But the ones responsible for the piece of shit that is CSS are actually W3C, Inc. Not that the bad looks of Google having them by the balls is better than your scenario eg the impression W3C on its last legs receiving money to keep the illusion of a multi-party effort of web standards.
But the ones responsible for the piece of shit that is CSS are actually W3C, Inc. Not that the bad looks of Google having them by the balls is better than your scenario eg the impression W3C on its last legs receiving money to keep the illusion of a multi-party effort of web standards.