Chrome is deploying HTTP/3 and IETF QUIC

Re:Chrome is deploying HTTP/3 and IETF QUIC by swiley on Wednesday October 07, 2020 @05:31PM (#24712971)

Most of it is garbage that doesn't need to be there and is shoved in people's faces because it makes other people money/power.

Ex: Why does clicking on a location link in google search load a big slow SPA to display a list of "cards" instead of just having a maps/web link in the search results?

[ Parent | on HN ]

Re:Chrome is deploying HTTP/3 and IETF QUIC by GrantZvolsky on Wednesday October 07, 2020 @07:35PM (#24714089)

I thought it's because Google isn't allowed to promote Google Maps in its search results, but a cursory search didn't yield any evidence.

Presumably if Search did link to Google Maps, other geographic information systems would have to be represented, just like various streaming platforms are represented in the video tab.

[ Parent | on HN ]

Re:Chrome is deploying HTTP/3 and IETF QUIC by Spivak on Wednesday October 07, 2020 @09:53PM (#24714840)

3% less garbage is still a lot. Would you rather more garbage?

[ Parent | on HN ]

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

3% less garbage is good, but 100% less would be preferable.

[ Parent | on HN ]