> Sign the manifesto: http://notcp.io . If you can figure out a way to sign it using UDP, let us know.
It's pretty clear they know they are being ridiculous.
That said, it is nice to have reminders that there are alternatives to the overwhelmingly popular default. Kids these days grow up using TCP so much they become devs who can't conceive of whole categories of software that don't happen to line up with the tradeoffs designed into TCP. Heck, seems like most people have a hard time remembering that there's more to the Internet than HTTP.
UDP while is very simple from design point of view is actually very complicated to use if you plan to do something more than just send few packets.
The issue is primarily, that you don't have a feedback loop that tells you the rate at which you should send the data. Also badly written applications that use UDP can create congestion collapse in a network (no congestion control/avoidance).
> Sign the manifesto: http://notcp.io . If you can figure out a way to sign it using UDP, let us know.
It's pretty clear they know they are being ridiculous.
That said, it is nice to have reminders that there are alternatives to the overwhelmingly popular default. Kids these days grow up using TCP so much they become devs who can't conceive of whole categories of software that don't happen to line up with the tradeoffs designed into TCP. Heck, seems like most people have a hard time remembering that there's more to the Internet than HTTP.