Re:Tracing HTTP Requests with Go's net/HTTP/httptrace
by melodyogonna on Monday June 01, 2026 @08:31AM
(#48355961)
Little things like this are why Go is great. People make arguments against Go based just on available language syntax, but languages are more than just syntax; it is about the end-to-end development flow. I actually think C# and the .NET platform are the only other ecosystem that looks at development the same way. In most other ecosystems, you almost always need to step outside what the built-in language platform provides for any moderately complicated use-case.
[ Parent
| on HN ]
Re:Tracing HTTP Requests with Go's net/HTTP/httptrace
by blainsmith on Monday June 01, 2026 @09:22AM
(#48356512)
I agree with you about C# there. I don't use it really at all, but the times I did it felt like I was writing Go with how nice the stdlib was and that I could just use the dotnet CLI on Linux too. It was pleasant and productive to use.
Re:Tracing HTTP Requests with Go's net/HTTP/httptrace
by systems on Monday June 01, 2026 @10:10AM
(#48357069)
do you mean use none core libraries / 3rd party libs
or using libraries from different languages like how some libs or frameworks from different languages create bindings to python libs
many C# libs are available via Nugets, which are not more or less complicated than other languages package managers
i personally think C# package management is more obscure, compared to other languages
Re:Tracing HTTP Requests with Go's net/HTTP/httptrace
by melodyogonna on Monday June 01, 2026 @10:21AM
(#48357217)
I mean that in both cases, the core language platform provides the tools and libraries you need to develop complete applications; you don't have to introduce external dependencies or resort to writing low-level data structures and data types.