this reminds that protocol compliance and performance aren't always aligned

Im not entirely sure what the motivation was for replacing nghttp2 with oghttp2 - nghttp2 is probably the most used codec for http/2 - so probably not compliance. I think it was mostly about code reuse since oghttp2 is part of QUICHE which is also used in Envoy for QUIC.

I'm curious if the primary customer will be developers or IT admins