Is there any reason why so many of those tools are written in Go? Is it because of a stdlib or just accidental?
Show HN: Doggo – A powerful, human-friendly DNS client for the command line
31–40 of 138 posts
Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line
#32Congrats for the 1.0 release!
doggo has been my main DNS tool for a while, now. Love it!
Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line
#33Is there any reason why so many of those tools are written in Go? Is it because of a stdlib or just accidental?
Go gets it done and for years to come.
Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line
#34Would be amazing is this tool would add support for the equivalent of query type ANY
Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line
#35Is there any reason why so many of those tools are written in Go? Is it because of a stdlib or just accidental?
Could be cultural. Go has a lot of exposure in the DevOps / cloud infrastructure space. Lots of stuff like k8s and Terraform (and its providers) are written in Go, and it competes with Python in popularity for internal tooling.
Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line
#36Amazing naming choice - doggos like to dig!
TIL there's also dog[1] Which is probably also common typo for "dig" [1] https://github.com/ogham/dog
I went to switch over to "dog" last week but it looks abandoned. I couldn't get a download to work because of outdated dependencies, and IIRC I couldn't get it to build, so I just gave up on it after seeing the latest release is 4 years old.
Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line
#37Is there any reason why so many of those tools are written in Go? Is it because of a stdlib or just accidental?
In this case it seems like the creator of this tool already knew golang so he used it.
From the readme:
> It's totally inspired from dog [0] which is written in Rust. I wanted to add some features to it but since I don't know Rust, I found it as a nice opportunity to experiment with writing a DNS Client from scratch in Go myself. Hence the name dog +go => doggo.
Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line
#38Is there any reason why so many of those tools are written in Go? Is it because of a stdlib or just accidental?
So the name can be a pun, of course.
Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line
#39Is there any reason why so many of those tools are written in Go? Is it because of a stdlib or just accidental?
Go is produces (mostly) statically compiled binaries by default. No runtime, no interpreter, no dependencies.
Python, Java, JavaScript, C#, etc. can't say the same.
Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line
#40Love this, thank you! Is there a way to query all DNS records? (I was surprised to learn that isn't the default.) This would be really helpful for troubleshooting people's Caddy questions (which are actually DNS problems).
You can't really query all DNS records these days anymore by using the ANY query type. The closest alternative is to run dig across all record types. At Andrew McWatters & Co., we use a small internal utility called digany(1)[1][2] that does this for you. [1]: https://github.com/andrewmcwattersandco/digany [2]: https://github.com/andrewmcwattersandco/digany/blob/main/dig... andrewmcwatters@Andrews-MacBook-Pro digany…
or AXFR... but it is allowed on even less places than ANY.