▲Tracing HTTP Requests with Go's net/HTTP/httptrace(blainsmith.com)
139 points by speckx 4 days ago | 5 comments
▲melodyogonna 5 hours ago
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.
▲blainsmith 4 hours ago
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.
▲systems 3 hours ago
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

▲melodyogonna 3 hours ago
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.
▲Xeoncross 1 hour ago
Nice! Tracking connection reuse is really important if you are running any kind of benchmarks or comparisons both as the author of a new tool / service and as the person evaluating different options or client libraries.

I've hit a lot of walls not ensuring I was using connection pools correctly even when the service I'm calling was local/docker. File descriptor exhaustion happens often if you're not careful.

▲blainsmith 4 hours ago
Author here... Thanks for sharing this. It has been fun to use while we get ready to launch https://probes.dev with tracing being core to the service.
▲s-macke 5 hours ago
I wish I had known this two years ago. I ended up writing my own embedded connection struct to trace these things [0].

  type Connection struct {
    net.Conn
    OnEventCallback func(clientClosed bool, serverClosed bool, err error)
  }
[0] https://github.com/s-macke/SlapperX/blob/master/src/tracing/...
▲blainsmith 4 hours ago
That get's the job done too for those events depending on what you need them for. httptrace could be heavy handed if all you want is simple events like you show.
▲Zambyte 5 hours ago
hn title mangling strikes again.