News for hackers. Stuff that matters.
Re:TCP Sucks by mnd999 on Tuesday May 05, 2020 @04:04PM (#23084319)
TCP pretty obviously doesn’t suck as it’s pretty much powered the internet for the last 30ish (maybe more) years. I’m sure it isn’t perfect for every purpose and maybe I can be improved but enough with the click bait.
Re:TCP Sucks by TheDong on Tuesday May 05, 2020 @04:26PM (#23084598)
Coal power obviously doesn't suck as its pretty much powered the planet for the last 100 years.

It's perfectly possible for something to both be incredibly popular and to suck. An appeal to popularity is certainly not better than a click-bait headline.

I'd argue that most of the stuff we use sucks in some ways as well; suck isn't an absolute term. TCP sucks in very specific ways the article talks about.

Re:TCP Sucks by nine_k on Tuesday May 05, 2020 @05:41PM (#23085414)
It's not just popularity; it's an adaptable enough design to work in the range from 150 baud acoustic modem links to 40 Gbit fiber optics. Not many designs can withstand that, no matter how hard people try.
Re:TCP Sucks by berbec on Tuesday May 05, 2020 @09:27PM (#23087051)
I'd suggest an update to your lower bound - avian carrier
Re:TCP Sucks by the8472 on Wednesday May 06, 2020 @07:43AM (#23089875)
To my knowledge that has only ever been deployed to send ICMP messages, not TCP. With a TCP stack tuned to give more lenient timeouts it might work but you'll need a lot more trips to do a whole connection setup and teardown.
Re:TCP Sucks by ape4 on Tuesday May 05, 2020 @04:09PM (#23084385)
Yeah, TCP is the worst protocol except for all the others.
Re:TCP Sucks by andoriyu on Tuesday May 05, 2020 @06:54PM (#23086076)
I always liked SCTP more than anything. I would like QUIC if it wasn't for mandatory TLS.
Re:TCP Sucks by klodolph on Tuesday May 05, 2020 @04:17PM (#23084478)
Complaining about the article’s title is no substitute for replying to the article’s content. Writing a provocative title is how you get people to read your article. If you have an opinion to share, you shouldn’t try to disguise it as a drab technical report. The article makes sound points and the title makes sense.

Compare “TCP Sucks” (easy to read—communicates, concisely, that this is an opinion piece, and what the opinion is)

or “Limitations of TCP” (misrepresents the article as informational)

Re:TCP Sucks by Animats on Tuesday May 05, 2020 @05:17PM (#23085163)
The author says "TCP sucks", and is promoting his own protocol. Iridium. Which he hasn't even designed yet. That's a bit much. We don't get to criticize his approach.

(Also, if you're designing a communications system, don't give it the same name as another communications system.)

TCP has its limitations, of course. It was designed to work over a wide range of connections, including dial-up, and it does. It's suboptimal for broadband server to client connections where big server farms from a small number of vendors dominate. Hence QUIC and HTTP/2/3. Still, those don't provide a huge improvement in performance.[1] Even Google merely claims "on average, QUIC reduces Google search latency by 8% and 3.5% for desktop and mobile users respectively, and reduces video rebuffer time by 18% for desktop and 15.3% for mobile users." That's marginal. An ad blocker probably has more effect.

The author is worried about the overhead of the three-way handshake, but the overhead of setting up TLS is far worse.

[1] https://conferences.sigcomm.org/imc/2017/papers/imc17-final3...

Re:TCP Sucks by throw0101a on Tuesday May 05, 2020 @05:21PM (#23085208)
> The author says "TCP sucks", and is promoting his own protocol. Iridium.

Well that won't be confusing at all:

* https://en.wikipedia.org/wiki/Iridium_satellite_constellatio...

Re:TCP Sucks by alyrik on Wednesday May 06, 2020 @10:44AM (#23091515)
> The author is worried about the overhead of the three-way handshake, but the overhead of setting up TLS is far worse.

Oh, "TLS sucks" is a whole separate blog post for another day ;-)

Re:TCP Sucks by bborud on Tuesday May 05, 2020 @04:51PM (#23084910)
If the title had been “Limitations of TCP for X” I would be more likely to read it than with its current title. For the simple reason that 9 out of 10 times, when people say “TCP sucks” they ignore all the things we ask TCP to do. Not least of which is “try not to break the Internet”.

I’ve tried to design stream transports on top of UDP. It is doable if the scope is narrow and you actually understand a bit of what went into other protocols (like TCP). But it isn’t easy.

Re:TCP Sucks by varjag on Tuesday May 05, 2020 @04:34PM (#23084717)
There is an unwritten rule that it is allowed to comment on clickbait articles without reading them.
Re:TCP Sucks by stestagg on Tuesday May 05, 2020 @04:39PM (#23084767)
There is a hitherto-unwritten rule that it is allowed to comment...