The other awesome thing about QUIC is that it encrypts almost everything including header information, making middlebox traffic shaping worthless and demoting middleboxes in general.

It also makes hardware offloads like TSO and LRO impossible, and increases cost-per-byte served by a factor of 4 or more. So if you have infinite CPU to throw at QUIC and/or low bandwidth or connection targets, its great. If you are concerned at all about server-side efficiency, its terrible.

FWIW, I work on the Netflix CDN, and specialize in server-side efficiency; we have had 100G flash CDN nodes for years serving at 90G+ in production. None of that would be possible with QUIC as it stands. I suspect our max B/W on these machines would drop from ~95Gb/s to 20Gb/s or less if we were to switch to QUIC.

I hear you and those are valid points.

Don't blame QUIC. Blame ISPs and middlebox makers for abusing their (literal network-wise) position and breaking the end-to-end principle. History has shown that we just have to encrypt everything and quite literally cut out the middleman/box.

Does the protocol actually make it impossible, or is it just not implemented by current OS/hardware?

Definitely just that the HW hasn't caught up.

https://www.netdevconf.org/0x13/session.html?talk-quic-offlo...

Can't wait for the IETF standardization process to finish up! https://quicwg.org/base-drafts/draft-ietf-quic-transport.htm...

You'll just get more JavaScript piled on as managers insist on having X monetization feature deployed.

This article is about mobile apps

Native mobile apps are great only because it's so much more difficult to pile on shit (newsletter signups, ads, GDPR popovers, etc)