> But HTTP/2 and QUIC are taking us back into the realm of non-standard and more rigid and opaque binary protocols.
This whole BINARY vs. PLAINTEXT paradox where the binary tends to be more efficient where the plaintext more open and intermediate ground between humans and machines, for me can be solved in a optimal way where the final output is always binary, but where you can assist humans with plaintext latter.
Just look how many beautiful and expressive computer languages we have now where the output is a pure obscure binary.
So i think if you follow this path you can have the best of both worlds. And because of that i tend to disagree with your point of view, where the default must be plaintext.. The layered approach is probably much more sophisticated and less amateurish when you care about waste of CPU cycles and RAM memory, without the need to have only a obscure and opaque representation.
This whole BINARY vs. PLAINTEXT paradox where the binary tends to be more efficient where the plaintext more open and intermediate ground between humans and machines, for me can be solved in a optimal way where the final output is always binary, but where you can assist humans with plaintext latter.
Just look how many beautiful and expressive computer languages we have now where the output is a pure obscure binary.
So i think if you follow this path you can have the best of both worlds. And because of that i tend to disagree with your point of view, where the default must be plaintext.. The layered approach is probably much more sophisticated and less amateurish when you care about waste of CPU cycles and RAM memory, without the need to have only a obscure and opaque representation.