3 ms·
> HTTP/2 cannot be easily read or written by a human with a telnet or s_client connection without some additional tools This is, of course, why we also don't u
by acdha 8y ago
> HTTP/2 cannot be easily read or written by a human with a telnet or s_client connection without some additional tools
This is, of course, why we also don't use chunked encoding and compression with HTTP 1 rather than writing better tools. I mean, you even have the example in that sentence about how the solution for using TLS was not to say “it doesn't work with telnet” but to use s_client, ncat, socat, etc.
> It also can't be supported by a lot of old software without some additional layer of indirection
This part is true but it's also the classic legacy computing problem: old software which cannot be upgraded will increasingly have security and compatibility issues which favor putting it behind a proxy anyway. This should factor into the cost of choosing not to maintain those systems rather holding back the future.
- skywhopper 8y agoHow is HTTP/1.1 holding anything back?
- acdha 8y agoHTTP 1 has a fixed feature set and a lot of warts. Nobody is working on HTTP 1.2, etc. so the only way anything is going to get better will be in the HTTP/2 series of development. At some point we need to ask whether skimping on maintenance is actually better than getting those improvements.