←back to thread

306 points carlos-menezes | 1 comments | | HN request time: 0s | source
Show context
Tempest1981 ◴[] No.41891085[source]
From September:

QUIC is not quick enough over fast internet (acm.org)

https://news.ycombinator.com/item?id=41484991 (327 comments)

replies(2): >>41891107 #>>41893876 #
lysace ◴[] No.41891107[source]
My personal takeaway from that: Perhaps we shouldn't let Google design and more or less unilaterally dictate and enforce internet protocol usage via Chromium.

Brave/Vivaldi/Opera/etc: You should make a conscious choice.

replies(3): >>41891197 #>>41891355 #>>41891374 #
vlovich123 ◴[] No.41891197[source]
So because the Linux kernel isn’t as optimized for QUIC as it has been for TCP we shouldn’t design new protocols? Or it should be restricted to academics that had tried and failed for decades and would have had all the same problems even if they succeeded? And all of this only in a data center environment really and less about the general internet Quic was designed for?

This is an interesting hot take.

replies(1): >>41891219 #
lysace ◴[] No.41891219[source]
I'm struggling to parse my comment in the way you seem to think it did. In what way did or would my comment restrict your ability to design new protocols? Please explain.
replies(1): >>41892122 #
vlovich123 ◴[] No.41892122[source]
Because you imply in that comment that it should be someone other than Google developing new protocols while in another you say that the protocols are already too complex implying stasis is the preferred state.

You’re also factually incorrect in a number of ways such as claiming that HTTP/2 was a Google project (it’s not and some of the poorly thought out ideas like push didn’t come from Google).

The fact of the matter is that other attempts at “next gen” protocols had taken place. Google is the only one that won out. Part of it is because they were one of the few properties that controlled enough web traffic to try something. Another is that they explicitly learned from mistakes that the academics had been doing and taken market effects into account (ie not requiring SW updates of middleware boxes). I’d say all things considered Internet connectivity is better that QUIC got standardized. Papers like this simply point to current inefficiencies of today’s implementation - those can be fixed. These aren’t intractable design flaws of the protocol itself.

But you seem to really hate Google as a starting point so that seems to color your opinion of anything they produce rather than engaging with the technical material in good faith.

replies(1): >>41892260 #
1. lysace ◴[] No.41892260{3}[source]
I don't hate Google. I admire it what for what it is; an extremely efficient and inherently scalable corporate structure designed to exploit the Internet and the web in the most brutal and profitable way imaginable.

It's just that their interests in certain aspects don't align with ours.