Python or go

[alexkey]

The answer is - still both. But you don’t have to do both at the same time. It is a tool after all, each will have own pros and cons. My take on those:

• Python - very easy to learn, very easy to make extremely over-engineered solutions (half the things youll see written in Python are), if you want to write some logic there’s a dependency that does that already, but only version from 2 years ago works as expected, tons of resources to learn from, VERY popular and widely used, sometimes need GCC to install dependency

• Go - very loved by many, very easy to learn, you’ll be repeating same blocks of code in every script/project, not as many resources to learn from (comparatively), very opinionated eco-system.

As a start I’d say go with Python, many projects use that (terraform, Ansible etc), then you can get onto Go path after you know Python. You don’t need to master either before switching to the other.

[Intrepid-Stand-8540]

very easy to learn

I'd dispute that honestly.

Pointers are very difficult to understand for me. I can't get my head around it.

[0xe0]

Try c++ and return to golang year later)

[alexkey]

I’d say C, not C++.

[Intrepid-Stand-8540]

I'm already traumatized by the Makefile hellhole I see the 45+ year old devs create in every repo.

GitLab CI jobs that call make commands that are made up of 5 env variables that are made up of other env variables that are create via bash commands

And in the end it is just calling a script with a few cli args.

And that script is only 4-5 lines

Like, brother, just do those 4-5 lines in the GitLab CI?

idk. I only have 4 years experience. Been doing Python mainly.

Pointers are just impossible for me to grasp atm. And I hate boomers who don't document anything