[DangitBobby]

It's just a little bit more work to write a non-trivial program in Go than in a scripting language such as Python, so if you need/want the good tooling and you need/want the significant speed improvement, it could be a good choice.

[__turbobrew__]

Go doesn’t have the libraries of python however. In certain computing domains you would first have to spend 10 years rewriting the python frameworks in golang before you could even be on parity with python.

I am most familiar with scientific computing and GIS applications — python is miles ahead of golang in ecosystem support in those domains.

[remexre]

For scripting and "just throwing something together for internal use," Python is a pretty traditional choice, but I think Go is able to outclass it for maintainability -- static typing and somewhat better package management are a big help, and Go has a comparable ecosystem.

[marsdepinski]

We'll see in another ten years

[kbenson]

If that was a useful argument for the future we'd all still be using Perl.

I mean, I still write a lot of Perl, but everyone else would be too.

[Zababa]

And if this wasn't a useful argument many more people would use OCaml, Crystal, D, etc ; and every new language wouldn't be met with "I like it but it doesn't have the libraries I need so I'll keep writing Java".

[copperx]

Naive question, can't you just call Python code from Go? I don't see the problem besides that performance of the Python libs wouldn't be as good as if they were written in Go.

[jiggunjer]

Julia makes the same claims