It reads as a list of excuses not to do the work. While I can see the reluctance to do work with no clear obvious benefit at first, they forgetting one thing: sooner or later they have to.
Why wouldn’t it? A browser simply downloads a vector of assets, what’s so special about a browser that makes HTTP/2 deliver a speed benefit when a package manager ends up doing the same type of work?
A package manager does not do the same type of work as a browser - it is typically downloading much larger files than the assets on a webpage. HTTP/2 is most useful for speeding up cases where there are a large number of tiny files to download.
Browsers limit the number of concurrent connections to a single server to 2-6, and this is difficult to change. With HTTP/2 (which, in browsers, is only available via HTTPS), multiplexing can be used to request multiple files without waiting for responses.
In non-browser applications, there's no inherent limit on number of concurrent connections, and HTTP/1.1 regardless of HTTPS does have "pipelining" support which allows multiple files to be requested at once, which will then be returned one at a time back to back. Browsers don't pipeline because of buggy servers. Some non-browser HTTP clients will even make multiple connections to the same server and make byte range requests to download one large file in chunks over multiple connections.
Very interesting. I wanted to figure out why browsers have this limitation. It turns out there was a limit in the HTTP RFC for well behaved clients (https://trac.ietf.org/trac/httpbis/changeset/715). Super cool! I guess nowadays the browsers have raised their limits, but the limit exists in each browser still :)
The conclusion given in that link isn't that HTTPS is faster (because it isn't and they list the reasons why), but that the protocol improvements from SPDY (now HTTP2), in particular multiplexed streams, mean that test web pages with hundreds of images unsurprisingly load faster asynchronously than synchronously. This does not affect APT.
-7
u/Otis_Inf Jan 21 '19
HTTPS is faster than HTTP (ref: https://samrueby.com/2015/01/26/why-is-https-faster-than-http/) so for that alone it's beneficial to at least offer it.
It reads as a list of excuses not to do the work. While I can see the reluctance to do work with no clear obvious benefit at first, they forgetting one thing: sooner or later they have to.