3 ms·

The whole article seems to have been motivated by the ex-MSFT engineer's comment, padded with some false impressions on how standards involve. HTTP2 and HTTP3

The whole article seems to have been motivated by the ex-MSFT engineer's comment, padded with some false impressions on how standards involve. HTTP2 and HTTP3 are decided by committees and it isnt Google who controls it. While I dont know whether the MSFT engineer's claims are true or not, but even with some benefit of the doubt, having an empty <div> cause such an obvious performance degradation sounds to be like hyper optimized for an implementation rather than actual breakthrough.

dblohm7 8y ago
> HTTP2 and HTTP3 are decided by committees and it isnt Google who controls it. That was then, this is now. What happens when Google implements its next protocol in Chromium? With Blink's market share, would they even bother with committees anymore? At this point, they could more or less get what they want out of it without the extra bureaucracy.
- dwild 8y ago
  > What happens when Google implements its next protocol in Chromium? With Blink's market share, would they even bother with committees anymore? They didn't bother for SPDY or QUIC. They were implemented in the browser, like many others features, before any committee. It's the committees though that decided to base their works for HTTP/2 and HTTP3 over theses. The danger isn't on what they implements, because that's already something they do (and all others browsers do), but based on what they DON'T implements. What if they ignore HTTP3 and only use a new protocol they made?