HTTP-over-QUIC will officially become HTTP/3
Garh.<p>So we are to believe that the people who thought that multiplexing a single TCP connection over mobile was a good idea, that moving lockstock and barrel to UDP will solve our problems?<p>Look, its very simple: HTTP is now a file server protocol with a chatty control channel smashed in. However instead of optimising for that we have this.<p>It basically seems like a massive ego trip: &quot;we can&#x27;t admit we were wrong about the multiplexing thing, lets just bash out a reliable UDP protocol&quot;<p>Look, the vast majority of file transfer protocols are TCP for a reason. Loosing chunks of files is annoying, and making a custom protocol over UDP that is both fast start reliable <i>and</i> fast, is actually quite difficult.<p>Yes, UDP has the advantage that you don&#x27;t have a connection, and you can just fire stuff at the destination port and it&#x27;ll magically arrive. however, <i>anyone</i> can do that. How does HTTP3 handle noise? how does it handle spoofing?<p>Basically, H2 was a regression because it was designed by people who didn&#x27;t appear to understand real world networks, this seems like a doubling down.