There is a very simple reason for not being on the list: It support HTTP/3 and the purpose of the post was to show the lack of support in common languages. .NET does not fit that list well.
And it is obviously only popular in the dark matter of Enterprise Software Development.
C# is much closer in popularity to TypeScript/Python (the number 1s) than it is to Rust.
In usage yes, in analysis yes but not in general popularity.
And to Rust ... definitely. Rust is a niche product for system development. A very good one. A very popular one. But nothing you need for your day to day microservice.
Re:HTTP/3 is everywhere but nowhere
by CharlieDigital on Tuesday March 18, 2025 @10:40AM
(#43400015)
> And it is obviously only popular in the dark matter of Enterprise Software Development.
Well, and apparently for game development given both Godot and Unity use C# and various builds of .NETI don't think many people use the builtin HttpClient these days. Apache httpclient would be the conservative standard, apparentyl it has some support for 2 but not 3: https://hc.apache.org/httpcomponents-client-5.4.x/index.html .
I just checked the Java class HttpClient (a common JDK11+ HTTP client). It currently does not support HTTP/3, so add one more to the list!
Ref: https://docs.oracle.com/en/java/javase/24/docs/api/java.net....
Also, most of the very best network clients are now built on top of NettyIO. I can see an "incubator codec" here: https://github.com/netty/netty-incubator-codec-http3
Holy hell, this code is ridiculously complex: https://github.com/netty/netty-incubator-codec-http3/tree/ma...
I'm not hating on NettyIO here, but the protocol looks complex. Yet another reason why it is so slow to be deployed to more application frameworks.