3 ms·

At this point both W3C and WHATWG are not where innovation on the web is (or should be) happening. It's up to the individual browser makers to innovate. W3C and

At this point both W3C and WHATWG are not where innovation on the web is (or should be) happening. It's up to the individual browser makers to innovate. W3C and WHATWG's job should be to document any consensus among browser makers. It shouldn't be their job to decide how browsers should work, that's the browser makers' decision. (Which happens to be large corporations, for the most part.)

Karunamon 9y ago
That just gets the browser makers castigated by the tech community. Every time, say.. Google, intents something new, the entirely predictable incoherent screaming starts about how it's another Microsoft IE/ActiveX. Nevermind the fact that the landscape has changed to the point where that isn't a realistic outcome anymore. Nevermind the fact that in the instance I'm describing (which was something like WebASM or WebSockets.. it was WebSomething and I can't recall the name), they had submitted their proposals to the standardization groups, with no change on the volume of the noises. I wish people would decide whether they want browser makers trying New Stuff or they want New Stuff coming from standards bodies only. There are upsides and downsides to either way, but I really don't beleive that BMing browser makers whenever they try New Stuff is even sort of constructive.
at-fates-hands 9y ago
> It's up to the individual browser makers to innovate. This seems to make the most sense because the browser is the end product by which people consume their internet. It seems to me, they have been and always will be years ahead of the governing bodies that make these part of their "standards" decisions. By the time something finally makes into the spec, we're already onto a dozen new things the browsers are capable of and implementing. At this point it just feels like the spec is an afterthought, not necessarily keeping up with how fast the industry is changing.
int_19h 9y ago
This is exactly how we got IE market dominance back in the day.

Karunamon 9y ago

That just gets the browser makers castigated by the tech community. Every time, say.. Google, intents something new, the entirely predictable incoherent screaming starts about how it's another Microsoft IE/ActiveX. Nevermind the fact that the landscape has changed to the point where that isn't a realistic outcome anymore. Nevermind the fact that in the instance I'm describing (which was something like WebASM or WebSockets.. it was WebSomething and I can't recall the name), they had submitted their proposals to the standardization groups, with no change on the volume of the noises. I wish people would decide whether they want browser makers trying New Stuff or they want New Stuff coming from standards bodies only. There are upsides and downsides to either way, but I really don't beleive that BMing browser makers whenever they try New Stuff is even sort of constructive.

at-fates-hands 9y ago

> It's up to the individual browser makers to innovate. This seems to make the most sense because the browser is the end product by which people consume their internet. It seems to me, they have been and always will be years ahead of the governing bodies that make these part of their "standards" decisions. By the time something finally makes into the spec, we're already onto a dozen new things the browsers are capable of and implementing. At this point it just feels like the spec is an afterthought, not necessarily keeping up with how fast the industry is changing.

int_19h 9y ago

This is exactly how we got IE market dominance back in the day.