I don't think of subsequent HTTP versions as replacing the previous ones - merely augmenting.
Re:Identifying QUIC deliverables
by marcosdumay on Monday October 29, 2018 @06:10PM
(#18332036)
So we'll need 3 servers instead of 1 just for serving HTTP?
Nginx can support HTTP 1.0, 1.1, and 2 all at once. I'd suspect one day it will be able to support 3 as well. And I'd imagine that any other server software of consequence is going to as well.
Re:Identifying QUIC deliverables
by marcosdumay on Monday October 29, 2018 @06:48PM
(#18332353)
Yes, and the more protocols running, the less likely it is to ever be replaced some day. Who has the time to write 2 (1.0 and 1.1 are basically equal) servers for a minimum package?
If somebody still sold HTTP servers, I would look how this one was bribing the standardizing process. But it looks like people are doing it freely.
I really can't figure out what you are saying. I don't see any evidence of bribery. And the technologies we're talking about have pretty legitimate reasons for existing. So, ...?
Re:Identifying QUIC deliverables
by ocdtrekkie on Monday October 29, 2018 @09:41AM
(#18327415)
Unfortunately, the low-level infrastructure of the web is now being controlled by a company which offers significant internal performance incentives for releasing new products.
QUIC is hardly a product - very few users will ever know what it is. That Google has significant influence on internet infrastructure is hard to deny - but saying they are in control is ridiculous. And a lot of that influence comes from hiring really knowledgeable people - ignoring them just because they work for Google would be silly, especially for something like QUIC that is open and generally useful.
Keep the web frontend culture contained where it is now, don't let them ruin everything else too.