Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

50% Positive

Analyzed from 130 words in the discussion.

Trending Topics

#performance#probably#interesting#read#bothered#write#codec#compliance#used#looks

Discussion (6 Comments)Read Original on HackerNews

basilikumabout 1 hour ago
this looks like it could be an interesting read that i would be bothered to read if a human bothered to write it.
dilyevskyabout 1 hour ago
I did write it, the machine did all the react tho (with my help)
adolphabout 1 hour ago
I found it worthwhile and interesting. I'm not in deep with proxies every day and have never had to profile performance like this. The writing was very comprehendable to me and the summing conclusions rounded things out nicely. The first conclusion was probably the most practical takeaway: Codec defaults are performance changes. Its obvious in retrospect but also easy to glaze over when reading release notes.
rightbondsadminabout 1 hour ago
this reminds that protocol compliance and performance aren't always aligned
dilyevsky36 minutes ago
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.
nosefrogabout 1 hour ago
So tired of these AI generated articles.