The answers to those two questions have not impressed me. So, if my bias is simply using basic logic to evaluate a language, then I think I'm going to keep using my "useless bias".
I also dislike Go the language, and I tend to write new things in Rust. But that's my choice as a dev. As a consumer of stuff other people have taken their own precious time to write and let me use for free ... No, I have no business telling them their choice of tool is wrong.
Stop giving Rust a bad name.
On my end I love Go executables because I know they’re fast, self contained with very little dynamic linking or dependencies, and I know I can (and do!) contribute easily.
I try to avoid Python tools because they depend too much on the installed Python version (even with 3+ I’ve had incompatibility issues), are generally slow (I use autojump because it’s best in class IMO compared to zoxide, z, or jump, but it’s slow as a cow), and sometimes suffer from bad error handling (the few Python tools I use like awscli routinely give me Python stack traces whereas Go or Rust tools rarely, if ever, fail that badly)
Now that you have an example, what are your arguments against Go tools?