3 ms·
For sure the "we've implemented this in Chrome already" aspect is a huge aspect in the standards process. I do think it's important to say that this isn't a su
by rtpg 9y ago
For sure the "we've implemented this in Chrome already" aspect is a huge aspect in the standards process.
I do think it's important to say that this isn't a sure-fire deal. We had stuff like NaCl (native code in the browser) that basically died off, and other options as well.
Inversely, SPDY is not what the standard is, and Google instead pulled stuff it learned into HTTP/2. This seems like a positive aspect to me.
It's important to be wary of things that Google won't bring up, but overall I feel like we're getting a lot of benefit from having an implementer "beta test" stuff in this way.