At first I wrote a lengthy rant about not supporting QUIC as an OSI layer 4 protocol on its own merits and develop HTTP to sit on top of either TCP or QUIC. But I'm hoping that the people pushing this along are only creating a homunculus guinea-pig, and that once this gets adopted widely, will push to turn QUIC out into a real independent low-level protocol like it should have been.

Bundling HTTP and QUIC into one protocol is a bad idea because (1) it increases complexity, (2) it creates application-specific QUIC implementations, which will become a problem later if QUIC is adopted by anything else, not to mention the security holes/feature gaps in different implementations, etc, (3) it reduces the likelihood of the operating system supporting QUIC as a first class L4(OSI) protocol, which will further doom any network application that uses any method of IPC other than an HTTP request.

Honestly, the way modern network applications operate is embarrassing. People in the future are going to look back and wonder what was wrong with us.