Chrome is deploying HTTP/3 and IETF QUIC

Re:Chrome is deploying HTTP/3 and IETF QUIC by stjohnswarts on Wednesday October 07, 2020 @11:47PM (#24715538)

How long before they rip out open source parts and make chrome closed source or a much more limited licensing and start sticking all their proprietary network protocols in it so that you can't fork Chrome any longer. I personally believe that's the endgame for google.

[ Parent | on HN ]

Re:Chrome is deploying HTTP/3 and IETF QUIC by jefftk on Thursday October 08, 2020 @10:50AM (#24719572)

> all their proprietary network protocols

We're literally discussing this on a post where Chrome is switching from a proprietary protocol (Google QUIC) to a standardized protocol (IETF QUIC).

(Disclosure: I work for Google, speaking only for myself)

[ Parent | on HN ]

Re:Chrome is deploying HTTP/3 and IETF QUIC by mda on Thursday October 08, 2020 @03:44AM (#24716854)

I don't think there a single instance of an application that Google did what you described. Why do you think it will start now? This doesn't make any sense.

[ Parent | on HN ]

Re:Chrome is deploying HTTP/3 and IETF QUIC by throwaway2048 on Monday October 12, 2020 @12:28PM (#24756135)

Google has been moving open source components of android into closed source Play store components for years now.

[ Parent | on HN ]

Re:Chrome is deploying HTTP/3 and IETF QUIC by lukeramsden on Thursday October 08, 2020 @02:50AM (#24716542)

That's a valid point, and a good one. I certainly hope they don't. Is there precedent for them doing something like that before?

[ Parent | on HN ]

Re:Chrome is deploying HTTP/3 and IETF QUIC by unionpivo on Thursday October 08, 2020 @04:19AM (#24717069)

Android without their proprietary bits is a lot less useful

[ Parent | on HN ]

Re:Chrome is deploying HTTP/3 and IETF QUIC by elcomet on Thursday October 08, 2020 @09:48AM (#24719063)

Hope is the only thing we got

[ Parent | on HN ]