It's a common argument that HTTP/2 being binary makes it harder to debug. Sure, it might be tougher if I'm using Wireshark to look at raw TCP packets. But Chrome/Safari/Firefox/IE Web Inspectors (what most web devs use to debug HTTP requests) already parse the HTTP the same way as before.
So I've noticed exactly 0 difference in my workflow between HTTP 1 and HTTP 2.
<strike>None for netcat (it's a bare-wire tool, and doesn't support HTTP/1.1 either)</strike>
sorry, I must have misread "socat" as "netcat". Since socat's HTTP integration is an HTTP proxy on port 8080 it should be transparent due to using "CONNECT" for https.
So I've noticed exactly 0 difference in my workflow between HTTP 1 and HTTP 2.