HTTP/3 explained
So much negativity in this thread.<p>Personally I am _very_ excited by HTTP&#x2F;3 (and QUIC), it feels like the building block for Internet 2.0, with connection migration over different IPs, mandatory encryption, bidirectional streams and it being a user-space library – sure, more bloat, but from now on we won&#x27;t have to wait for your kernel to support feature X, or even worse, your ISP-provided router or decade old middleware router on the Internet.<p>I haven&#x27;t had the chance to read the actual spec yet, but it&#x27;s obvious that while the current tech (HTTP2) is an improvement over what we had before, HTTP&#x2F;3 is a good base to make the web even faster and more secure.<p>HTTP&#x2F;3 won&#x27;t be IPv6: it only requires support from the two parties that benefit from it the most: browser vendors and web server vendors. We won&#x27;t have to wait on the whole internet to upgrade their hardware.