Being able to build Go into a binary without any dependency makes distribution really easy. As a user I prefer a single file that I can download and run and as a developer it has really simplified builds and deploys.
agreed. for a user to get a python cli to work they will need to install python and any open source libraries your cli depends on (unless you use some tool to bundle all the dependencies with your app, in ye olden days this was py2exe or similar for bundling for windows).
similarly, for java you place the burden on your users to install a jre
with go the standard build toolchain lets you easily cross-compile a bunch of statically linked binaries, so each user just downloads 1 file for their target platform and runs it.
personally i am much more productive writing code in python than in go (this is largely a consequence of spending 20x as much time writing python than go) but go is dramatically more ergonomic from a deployment perspective and has a great cross-platform library and cross-compiler support out of the box
similarly, for java you place the burden on your users to install a jre
with go the standard build toolchain lets you easily cross-compile a bunch of statically linked binaries, so each user just downloads 1 file for their target platform and runs it.
personally i am much more productive writing code in python than in go (this is largely a consequence of spending 20x as much time writing python than go) but go is dramatically more ergonomic from a deployment perspective and has a great cross-platform library and cross-compiler support out of the box