pingtrace 1.0: why I rewrote from npm to Go

In March I shared the first version of pingtrace here on DEV.

That version answered the initial question: could I make the first minutes of a network troubleshooting session clearer by combining the commands I already run every day?

The answer was yes.

But after building more features, I realised the most important design decision was no longer the table layout or another flag. It was how a troubleshooting tool reaches the machine where it is needed.

Today, pingtrace reaches its first stable release as a Go CLI distributed as standalone binaries, with v1.0.1 being the current release.