4 ms·

Translation: Making the network more efficient enbiggens the amount of excrement you can put in that bag. Efficiency bad!! ? > Edit: Of course I d

Translation: Making the network more efficient enbiggens the amount of excrement you can put in that bag. Efficiency bad!! ? > Edit: Of course I didn’t read the article, but now I did and it’s somehow worse than I thought. “Why TCP is not optimal for today’s web”: no answers. There are literally no answers here. Other than, TCP is old. Old things are difficult. I think you just didn't read the article period. That QUIC hides a lot of metadata that TCP doesn't was covered, for example, and there's stuff about multipath, etc. And clearly, yes, TCP is old, and a lot of the extensions done to it over the years (e.g., window scaling, SACK) are great but still not perfect (especially window scaling) and it's getting harder to improve the whole thing, and then there's congestion control. But TCP was never going to be replaced by SCTP because SCTP was a new protocol number above IP and that meant lots of middleboxes dropped it, so any new thing would have to be run over UDP, and it would have to be popular in the big tech set, else it wouldn't get deployed either.

SanderNL 3y ago
“Efficiency” for whom and for what? Think deep before you all bow down before our overlords and ditch clear and simple protocols for “efficiency”. I know what QUIC is for and I know it’s strengths. I just want the web to be simple and accessible. It’s great Netflix and friends can stream content efficiently. It’s another thing to push this to the “open web” and declare it The Protocol.
- Dylan16807 3y ago
  Sometimes a webpage just wants to have a bunch of images, which is not a bad thing, and something like this helps it load better. > It’s great Netflix and friends can stream content efficiently. This barely affects streaming. Streams work fine with a single TCP connection.

SanderNL 3y ago

“Efficiency” for whom and for what? Think deep before you all bow down before our overlords and ditch clear and simple protocols for “efficiency”. I know what QUIC is for and I know it’s strengths. I just want the web to be simple and accessible. It’s great Netflix and friends can stream content efficiently. It’s another thing to push this to the “open web” and declare it The Protocol.

Dylan16807 3y ago
Sometimes a webpage just wants to have a bunch of images, which is not a bad thing, and something like this helps it load better. > It’s great Netflix and friends can stream content efficiently. This barely affects streaming. Streams work fine with a single TCP connection.