News for hackers. Stuff that matters.

A comment on Chrome is deploying HTTP/3 and IETF QUIC. Parent comment

Re:Chrome is deploying HTTP/3 and IETF QUIC by zmj on Wednesday October 07, 2020 @08:16PM (#24714344)
People argue both sides of this. If Google implements a new protocol on their servers and their clients without standardizing it, they're end-running the standards process or embrace-extend-extinguishing the open internet. If they do standardize it and then deploy the standard implementation, they're.. I don't even know, making billions of page loads faster and that's bad because they're Google?

What's the right way for Google to improve their internet-facing services at a protocol level?

[ Parent | on HN ]
Re:Chrome is deploying HTTP/3 and IETF QUIC by millstone on Thursday October 08, 2020 @01:54AM (#24716280)
The underlying concern is that Google is in a position to dictate. They control most phones and most browsers and the most popular websites. Any standardization is pro forma, because what matters is what Chrome/Android/google.com does, and not what the standard says.

An emperor can build trust by relinquishing power.

[ Parent | on HN ]
Re:Chrome is deploying HTTP/3 and IETF QUIC by mariusmarais on Thursday October 08, 2020 @05:55AM (#24717568)
What you're proposing as a solution has already happened: Google relinquished their control over this protocol to the IETF, where it changed so much as to be incompatible with Google's original.

Now they're updating their own deployment, making it compatible with the updated standard.

Chrome/Android/google.com is literally changing what they do to match what the standard says.

[ Parent | on HN ]
Re:Chrome is deploying HTTP/3 and IETF QUIC by KyeRussell on Wednesday October 07, 2020 @08:58PM (#24714579)
I imagine that a prerequisite is to hire every person that'd complain about this stuff on Hacker News, so that they'd be on Google's team.
[ Parent | on HN ]