<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>an_opabinia</author><text>As another user stated, the biggest advantage of QUIC is how much more sense it makes for wireless communications and mobile devices. Mobile networks break TCP connections all the time, it just violates too many useful assumptions of TCP.&lt;p&gt;HTTP&amp;#x2F;3&amp;#x27;s WebTransport (i.e. gRPC + sessions) defines a Session far more logically than a TCP Connection + your ad-hoc in-application Session does.&lt;p&gt;The predecessors of WebTransport already appear every everywhere in low-latency and realtime networked applications, like games, chat and video, on mobile devices. Typically that is achieved using UDP + an ad-hoc session management and authentication protocol. Or worse, undoing TCP connections and managing sessions on top of TCP connection breaks (as most dual web + native applications do).&lt;p&gt;Why reinvent that clumsy stuff over and over again instead of having it standardized? TCP is already dead on mobile, for many of the most popular applications people actually use.</text><parent_chain><item><author>coddle-hark</author><text>I’m not an expert but QUIC doesn’t seem like enough of an improvement over TCP to warrant replacing it, especially given that it’s even more complex.&lt;p&gt;- 0-RTT handshakes are great but there’s still the problem of slow start.&lt;p&gt;- QUIC’s congestion control mechanism is pretty much the same as TCP’s and doesn’t perform particularly well over e.g. mobile networks.&lt;p&gt;- Mandatory TLS means it’s going to be a huge PITA if you ever need to run a quic service locally (say, in a container).&lt;p&gt;- Having it in user space means there’a a good chance we’ll end up with 100s of implementations, all with their own quirks. It’s bad enough trying to optimise for the three big TCP stacks.</text></item></parent_chain></comment><story><title>Chrome is deploying HTTP/3 and IETF QUIC</title><url>https://blog.chromium.org/2020/10/chrome-is-deploying-http3-and-ietf-quic.html</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>mcqueenjordan</author><text>No head-of-line blocking is a pretty significant improvement.</text><parent_chain><item><author>coddle-hark</author><text>I’m not an expert but QUIC doesn’t seem like enough of an improvement over TCP to warrant replacing it, especially given that it’s even more complex.&lt;p&gt;- 0-RTT handshakes are great but there’s still the problem of slow start.&lt;p&gt;- QUIC’s congestion control mechanism is pretty much the same as TCP’s and doesn’t perform particularly well over e.g. mobile networks.&lt;p&gt;- Mandatory TLS means it’s going to be a huge PITA if you ever need to run a quic service locally (say, in a container).&lt;p&gt;- Having it in user space means there’a a good chance we’ll end up with 100s of implementations, all with their own quirks. It’s bad enough trying to optimise for the three big TCP stacks.</text></item></parent_chain></comment><story><title>Chrome is deploying HTTP/3 and IETF QUIC</title><url>https://blog.chromium.org/2020/10/chrome-is-deploying-http3-and-ietf-quic.html</url></story>