(Any introduction on QUIC will explain you these if you are interest.)
If no, then QUIC has failed its purpose, for the tech-savvy browser users at least.
If yes, I'd be happy.
I'm also very afraid of the future of Web Assembly.
Both of these technologies i'm afraid aren't going to make things better, faster and more lightweight. They are just going to allow the bloat of the web to become worse without noticeable symptoms.
This is a problem with computers in general. For example IDEs and simple electron apps taking huge amounts of memory.
But if browsers like Firefox find a way to skip ahead in the stream (through the ads/trackers while never downloading/parsing them in the first place) then things could be back to normal (for us the ad-blocker users).
Still though, if used for good, QUIC (or HTTP/3) seems like a pretty good piece of tech.
I should have worded my comment better. It wasn't a claim, it was more like a "I think Google wants this protocol to succeed for their own ulterior motives (serve ads and impede blockers), but is that what is actually going to happen?".
All this is only a win mostly if you have a huge number of little assets from different sources. Ads, trackers, icon buttons, malware, etc. If it's all coming from one source, HTTP/2 is good enough. If it's mostly one big file, HTTP/1 is good enough.