Golang vs. Python: The Ultimate Battle in DevOps

I'm assuming dev teams that are responsible for deploying, observing, and maintaining microservices (which obviates the discussion about shared services). For cloud the physical servers/infrastructure is managed by AWS/GCP/Azure; for on-prem k8s the infrastructure team (what older devs used to call "sysadmins") provide the hardware onto which to deploy our convoluted microservices.

this is me experience aswell.

Most of the times devs doing ops works ends in a nightmarish setup which is hard to maintain.

There is a reason specialization exists, and having seperate ops folk can save you a tremendous amount of money on resources or/and hardware.

Go is good for infrastructure as code and automation since it compiles to native binaries.

Unfortunately the article neglected to mention that, which imo is the most useful aspect of go for devops, since no one wants to deal with runtime dependencies for hundreds of machines.

This reads like it was written by ChatGPT and provides no specific insight into Golang or Python from a devops perspective. It doesn't talk about which one is easier to use to actually automate your ops (definitely Python) or which one is easier to deploy (definitely Golang.) Flagged, waste of time.

I hope we quickly arrive at a social standard where posting AI-written content is viewed as extremely disrespectful to your audience.

EDIT: based on previous submissions it looks like aoms is the author of this post. Aoms, am I misunderstanding something here? Why are you doing this?

Focusing on on performance, seriously?

I'm more sysadmin than devops, but how fast you can script over something for a quick automation is the defining trait for most devops tasks, not performance. Going for performance is closer to dev than to ops. Using APIs of several systems doesn't need so much performance neither, unless you are doing pretty intensive amount of calls (and the backend/network could be more of a limitation than the language you use in your side).

Yes, the performance and one-file-deploy are Go advantages against python performance (not for that much) and dealing with dependences and versions. But that is not the whole story, at least for most of the tasks I had to deal with.

And it is not "or". You may want to decide between python or i.e. perl for scripting language used for automation, but there are things that should be addressed with python, and others with go.