I use `bore` which works about the same, interesting to see new options!
https://crates.io/crates/bore
Show HN: Doggo – A powerful, human-friendly DNS client for the command line
111–120 of 138 posts
Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line
#112Earlier quoted context omitted.
1. You have to audit/trust any software whether or not it’s distributed as part of your OS 2. What is there to configure? 3. It’s a Go program, so compilation happens transparently on installation provided the developers don’t release broken code. This isn’t the C/C++ world where you have complex bespoke build systems that only seem to work on the developers’ machines.
1- If you are claiming you are auditing all your OS parts, not even your own mother believes you, are you delving into tcp.c and ps2.c? delusional 2- I meant run the configure file. Typically configures in what folder you install the program, under what user, that kind of stuff. I'm just alluding to the whole open source installation process, which is more complex than installing an .msi on Windows, or installing an…
Then don't use it. No is forcing you. No need for all the whining here.
Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line
#113Another shameless plug for my website, you can use ipkitten.com to get your public IP address from your terminal: $ curl ipkitten.com 27.44.144.144 And if you visit it in a browser, you get your IP address and a kitten GIF!: https://ipkitten.com
I love using ipinfo.com for the extra details it provides like hostname, ISP, ASN, etc. $ curl ipinfo.io/json or you can look up these details for any other IP: $ curl ipinfo.io/18.18.18.18
We have a CLI as well: https://github.com/ipinfo/cli
It has a ton of bells and whistles, including summarize IPs, bulk enrichment, grepip, and a ton of network-related tools. I was writing a series of blog posts on the CLI, but I think the series got too long and left users to discover the features of the CLI on their own.
Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line
#114Is 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.
Yeah exactly. I wrote one orchestration tool in Python, another department used Go. Right now I'm using nodejs simply because that's the main project language and all the developers can help out :)
Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line
#115Very nice to also have it dockerized. You might just want to add in the documentation the `--rm` parameter for cleanup after running and `-t` for the colors. So it will be docker run --rm -it ghcr.io/mr-karan/doggo:latest mrkaran.dev MX
Just curious, but why go through all the trouble to create a docker container for a DNS cli utility with no dependencies?
Long answer: Not OP, but sometimes you’re in a throwaway env and want to quickly do a DNS query and don’t have any tools (like Ubuntu minimal) available. Spawning an ephemeral container isn’t a bad idea in that case.
Short answer: Why not :)
Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line
#116Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line
#117Very nice to also have it dockerized. You might just want to add in the documentation the `--rm` parameter for cleanup after running and `-t` for the colors. So it will be docker run --rm -it ghcr.io/mr-karan/doggo:latest mrkaran.dev MX
Just curious, but why go through all the trouble to create a docker container for a DNS cli utility with no dependencies?
Makes it easy to drop it into a k8s cluster, maybe?
Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line
#118Earlier quoted context omitted.
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.
That seems crazy to me that a DNS client is broken after only 4 years due to incompatibility dependencies! I was going to suggest that maybe it's just completed software, but wow, this makes me really want to stay away from the Rust ecosystem.
Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line
#119Earlier quoted context omitted.
Correct me if I am wrong. but this is the feature of C#/.Net as well as of recent versions.
dotnet publish -o . -p:PublishAot=true :) To be fair, I do not think the author understands what static binaries are and why they may or may not want them, and how what Go does differs to what C/C++ toolchain does. I’d be very surprised if they do, being a Go developer. Next time they will learn another excuse to promote their language.
Also to be fair, they did say "by default", and those options you provided must be set because they are not default.
Re: Show HN: Doggo – A powerful, human-friendly DNS client for the command line
#120Reminds me of https://github.com/ogham/dog
From the doggo github readme: > It's totally inspired from dog 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.
I do always find it interesting when people just want to add some features, and the language stops them from doing it. I'm so used to bouncing back and forth between code and docs (api docs and language syntax docs depending on my familiarity) that the language itself is basically an implementation detail that I don't really care about. There are very few languages that would even give me pause, let alone avoid modifying the project entirely.