It is a complex, stateful (!!) protocol with non-trivial state-machine. A "console app" won't cut it. Even Wireshark might not cut it. Thanks to things like qui

It is a complex, stateful (!!) protocol with non-trivial state-machine. A "console app" won't cut it. Even Wireshark might not cut it. Thanks to things like quick start, TLS session tickets and server push you won't understand what are you even looking on 90% of time. When HTTP 1.1 fails, your browser shows you a proper error message. When HTTP 2/3 fails, it is always "a protocol format violation". What violation? Why? Who knows. > I don't agree that this particular concern is large enough to slow adoption Sure thing. Kerberos is still alive and kicking. SMB 1 is built into every appliance. SOAP is the protocol of choice for corporations... Complexity never slows down adoption of <insert name of utter turd technology>, because such technology is generally being pushed down people's throats by someone else. If Google does not push HTTP 3 slower, it's adoption won't slow down. The quality of tech plays no role in that.