Can you quote the section of the article where it says that? Because the only reference to HTTP/1.1 I found says:
> HTTP/2 [...] provides several performance optimizations compared to HTTP/1.1. These optimizations include more efficient header compression, server push, stream multiplexing over the same connection, etc.
Iām curious how HTTP/2.0 and HTTP/1.1 compare in a few years from now.
Why is this a downside (apart from 'I can't telnet now')?
Binary ruins that fine tradition for the promise of 0.1% better performance. And I think that's a terrible trade.
I would say even say most networking protocols are binary. Some very high level protocols are not, but in my opinion working with binary ones in applications and libraries is much easier (no need to read an arbitrary amount of bytes and loop through all of them just to find a termination sequence, etc.)
(Edit: I realise you can likely also access/debug HTTP/2.0 streams with a CLI tool - I am currently ambivalent about text vs binary streams.)
It's even the backbone for the new Google RPC framework: gRPC allowing for microsecond latencies. It's time to move on to better tech.
Reading your other comments, it seems you have some anti-Google political stance rather than a technical basis for this.
How about we just ditch HTTP/2.0 (aka the Google forced it upon us protocol) and get back to something which is proven, IETF/W3C-based, is not binary, is simple and most importantly: actually works?
That'd be real nice.
Also let's not let Google create more internet protocols please. That'd also be nice.