News for hackers. Stuff that matters.
Re:Working Group Last Call: QUIC protocol drafts by Traubenfuchs on Wednesday June 10, 2020 @10:28AM (#23477354)
I see a chicken egg problem: Why would developers/companies abandon non-QUIC versions of their software if there is a significant chance users can't use it? (If they even implement it under those conditions at all.)
Re:Working Group Last Call: QUIC protocol drafts by Orphis on Wednesday June 10, 2020 @11:14AM (#23477953)
You don't, you run them in parallel to HTTP/3 and it shouldn't add any cost for you. The work is done in the browser (or any client) to fallback to whatever works.

Then, in a few years, when you notice that most of the traffic is done over QUIC, you still won't do anything as it has no significant cost anyway and helps the few % of people who haven't upgraded their network. And customers who can use it won't notice much as your website still works anyway, but your latency metrics should be better for those users.

Re:Working Group Last Call: QUIC protocol drafts by cryptonector on Wednesday June 10, 2020 @11:10AM (#23477901)
Because the semantics of HTTP don't change in /2 and /3, you can always put a reverse proxy in front to bridge versions.