3 ms·

> they have multiple people on the committee in charge of WebAssembly who have veto power Note that even if Google did not have people on that committee, they'

by est31 7y ago

> they have multiple people on the committee in charge of WebAssembly who have veto power Note that even if Google did not have people on that committee, they'd just not implement the feature in their browser, and the feature would be dead in the water. Outside of niche cases where browser choice is controlled, no web dev would adopt features that > 70% of users can't use. So the committee only reflects power dynamics that exist in the greater browser sphere. In fact, non-Google browsers probably have more seats than they have influence by raw market share.

leoc 7y ago
> So the committee only reflects power dynamics that exist in the greater browser sphere. It doesn't only reflect them, but also amplifies them. Quietly nobbling things in committee is surely a lot easier than having to field questions about why you aren't implementing Web standards (insert quotation marks as desired). There's also the danger of being embarrassed when someone writes a library which runs slowly on your browser and fast on others.