QUIC replaces TCP and is on IETF standards track. HTTP/2 replaces HTTP/1.1 (and is a direct descendent of SPDY, which has origins ~2009). HTTP/2 on TCP gets y

QUIC replaces TCP and is on IETF standards track. HTTP/2 replaces HTTP/1.1 (and is a direct descendent of SPDY, which has origins ~2009). HTTP/2 on TCP gets you some of the benefits that QUIC provides (multiplexing, reduced roundtrips), but HTTP/2 on QUIC is the best of both worlds. IMO, there's not much noise about QUIC mainly because most people don't care enough about latency to care, and the current lack of production-quality QUIC server software makes caring more complicated than "just enable it", so low demand all around. This should pick up when it gets closer to a ratified standard.