The comment you’re replying to is asking about the right tool for a particular domain, nothing about “the context of a statically typed language.”

Those are pretty inconsequential differences all things considered. Go Interfaces actually stand in for enums quite well when used the right way. I like pattern matching a lot but the difference vs A type switch statement in Go is relatively minor. These features are not uniquely helpful in writing CLIs, at least not to the level where they justify investing in learning a new language.

Static compilation and in particular, static linking help make CLI tools universal. Beyond that, it’s hard to say, because CLI tools can do such a wide range of things.

Is a single build config all that’s required to statically link these days (incl. when targeting windows and macOS)? Been a while since I tried but last I checked, there are still issues that you have to deal with yourself. This blog post seems to indicate that some fidgeting remains required. If not, great, dynamic linking is the devil