Debug Dockerized Go application using debugger and Hot-Reload

Debug Dockerized Go applications much better

An alternative to stack traces for your Go errors. Contribute to bracesdev/errtrace development by creating an account on GitHub.

Hey HN, I tend to use printf-style debugging as my primary troubleshooting method and only resort to gdb as a last resort. While I like its ease of use printf debugging isn't without its annoyances, namely removing the print statements once you're done. I used to use trace-level logging from proper logging libraries but adding trace calls in every corner quickly gets out of control and results in an overwhelming amount of output. To scratch my own itch I created dlg - a minimal debugging library that disappears completely from production builds. Its API exposes just a single function, Printf…

Hey HN! I just released go-nbd, a lightweight Go library for effortlessly creating NBD servers and clients. Its a neat tool for creating custom Linux block devices with arbitrary backends, such as a file, byte slice or what I'm planning to use it for, a tape drive. While there are a few partially abandoned projects like this out there already, this library tries to be as maintainable as possible by only implementing the most recent handshake revision and baseline functionality for both the client and the server, while still having enough support to be useful. I'd love to get your feedback :)

I've created a powerful tool to help Go developers uncover the hidden giants in their compiled binaries. Go Size Analyzer is like an X-ray machine for your Go executables, revealing: Which dependencies are eating up your binary size Unexpected bloat from standard library or vendor packages Size changes between binary versions with a visual diff Key features that set it apart: Interactive treemap visualizations (check out the demo: https://gsa.zxilly.dev) Slick terminal UI for deep diving into package hierarchies Cross-platform support (works on Linux, macOS, and Windows binaries)…