Using HTTP/2 Cleartext for a server in Go 1.24

It has a bit, but there are fundamental issues. Given the way the Go runtime wants to deal with reading and writing sockets, HTTP/2 requires 2 extra goroutines per connection, and the bouncing around over channels that this implies. This might not be a law of physics but there isn't another obvious way to do it in Go.

In the past when I wanted a really fast Go service using HTTP/2 I put the HTTP server in a C++ subprocess that handled the sockets and communicated with the Go application over a pipe. That was nice and fast, avoided the congestive collapse that Go suffers with too many runnable goroutines.

which would be pretend doing it, make 1000 mistakes then say "you're absolutely right" after you point to it's fuckups

To use a Analogy, AI is acting like pip install library in this case. Do you really want to do performative acts of Sisyphus or are more interested in end result?

Except you can do http1 requests in bash easily and many http3 libraries are bad anyway so you don't get the advantages of using it.

I wanted to do something fast using http3 but it ended up being way faster using ad-hoc code I wrote using http1. It would be even faster if I did it with http3 but hand writing for that protocol is a nightmare so here we are…

edit: downvoting me will not change the reality.

I'd much rather http2/3 with an expired cert over cleartext anyday.