This article is from last November. The Google group response linked from the post <a href="https://groups.google.com/a/chromium.org/forum/m/#!topic/proto-quic/xoooxrixCis" rel="nofollow">https://groups.google.com/a/chromium.org/forum/m/#!topic/pro...</a> implied many performance problems would be fixed within 2 weeks. I wonder how it's improved.
QUIC is a great idea in general, but in my personal opinion, it has a lot of weird Google-specific, application- and HTTP-level hacks hanging off of it -- e.g. 'orbit' server state in Snap Start -- and a singular focus on web service/browser receipt and how the thing works with SPDY, and that's unfortunate.<p>The internet does need a faster, multiplexed UDP streaming protocol with great encryption support. If only it weren't tied to the assumption of odd infrastructure.<p>(edit: I understand why Google's doing it this way; just wish they started from the bottom layer and worked their way up, rather than starting on all layers and working around to the sides)