Author of the post here. Good comments. I was being deliberately provocative in the title to make a point. As I note in the article, it may or may not turn out that QUIC replaces TCP; the main point is that we didn't need a "TCP replacement" as much as we needed something new to meet the requirements of RPC (and HTTP in particular) and QUIC is doing that nicely. It may turn out that is all we need and TCP disappears, but as you say, there are reasons to doubt that including the extent to which TCP is baked in to existing systems.
Comments
Author of the post here. Good comments. I was being deliberately provocative in the title to make a point. As I note in the article, it may or may not turn out that QUIC replaces TCP; the main point is that we didn't need a "TCP replacement" as much as we needed something new to meet the requirements of RPC (and HTTP in particular) and QUIC is doing that nicely. It may turn out that is all we need and TCP disappears, but as you say, there are reasons to doubt that including the extent to which TCP is baked in to existing systems.