quic is definitely great. however, HTTP2 has spent more than 10 years to be widely adopted by client side. I am not sure when HTTP3 would be widely used by browsers.

I really like the QUIC protocol. It’s multiple reliable channels and built-in security is awesome. We can still do ‘unreliable’ channels via normal UDP (though I wish we could have unreliable channels in QUIC so we wouldn’t have to manage a secondary set of encryption). What I wish it had were an unordered channel, where you could send small packets that would be guaranteed to be received but the order doesn’t matter, rather just as fast as possible is what matters and for them to ‘eventually’ arrive, it especially could keep the held memory open for the buffered data smaller as well as the increased speed.

It already is in Chrome (and similar ones like MS Edge) and Firefox (and google says that even Safari, the IE of the modern times, supports http3 too), unsure about that rest, but those encompass the vast vast amount of browsers out by a monstrously huge degree.