Yeah, more details will help. Without knowing more, here are some thoughts:

  • Python might be more “practical”, all else equal.
  • Go probably looks better on a resumé, all else equal.
  • Python has the big academic/data community, and has a ton of supporting libraries for this kind of work.
  • Go has features built more specifically for scaling and was developed with some “modern” problems in mind. But nothing’s a silver bullet.

Those are some thoughts from what I know of each language/community. I may have oversimplified some of the points but I think that’s a decent gist.

 

I'm a huge fan/primary user of Go but I also love Python since that was my first proper language; I totally agree with these comparisons. One thing I would add that I've found immensely helpful is the incredible documentation and explanatory pieces available through the official Go organization. It's a very knowledgeable community that explains things clearly (not that other groups aren't, it's just what I've found to be the case with Go).

It's a very knowledgeable community that explains things clearly

This! The Go community really seems to be inspired to crack hard problems and hand-hold noobs like me at the same time. :)

code of conduct - report abuse