Regardless of the adoption rate of QUIC, TCP is going to stick around for many, many years. The existing installed base requiring it is just too enormous.
But I wonder... if QUIC does end up entirely supplanting TCP, that means it's an entirely different networking scheme. We'd no longer be using TCP/IP at all, but something else. QUIC/IP?
Regardless of the adoption rate of QUIC, TCP is going to stick around for many, many years.
I agree with this and would add that the HN crowd is very HTTP browser and API centric. There are hundreds of thousands of applications that will be using TCP and not be updated until the internet is shut off. This is especially true for B2B applications. Just getting them to update cipher protocols is like pulling teeth, each time. There are an amazing number of "business critical" applications that are running ancient libraries, protocols, etc...
TCP and UDP will never go away but browsers and some API libraries may stop using TCP. More likely additional Layer 7 protocols may get added to TCP and UDP and people will use what works best for their application needs.
Isnt the main disadvatage of TCP over UDP, overhead, present only in unreliable connections? Afaik, when there is no loss or congestion, TCPs roundtrip or ordering does not cause significant delay.
So how relevant are the benefits you listed (faster development, multiplexing, congestion control) for residental end points? I am sceptical.
Regardless of the adoption rate of QUIC, TCP is going to stick around for many, many years. The existing installed base requiring it is just too enormous.
But I wonder... if QUIC does end up entirely supplanting TCP, that means it's an entirely different networking scheme. We'd no longer be using TCP/IP at all, but something else. QUIC/IP?
Regardless of the adoption rate of QUIC, TCP is going to stick around for many, many years.
I agree with this and would add that the HN crowd is very HTTP browser and API centric. There are hundreds of thousands of applications that will be using TCP and not be updated until the internet is shut off. This is especially true for B2B applications. Just getting them to update cipher protocols is like pulling teeth, each time. There are an amazing number of "business critical" applications that are running ancient libraries, protocols, etc...
TCP and UDP will never go away but browsers and some API libraries may stop using TCP. More likely additional Layer 7 protocols may get added to TCP and UDP and people will use what works best for their application needs.
Isnt the main disadvatage of TCP over UDP, overhead, present only in unreliable connections? Afaik, when there is no loss or congestion, TCPs roundtrip or ordering does not cause significant delay.
So how relevant are the benefits you listed (faster development, multiplexing, congestion control) for residental end points? I am sceptical.
Bench wireguard (kernel not userland) against an ssh tunnel and you’ll know…