this post was submitted on 31 Jul 2025
40 points (95.5% liked)

Programming

21981 readers
133 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
UlrikHD@programming.dev
40
is it worth learning golang? (sh.itjust.works)
submitted 6 days ago by thetreesaysbark@sh.itjust.works to c/programming@programming.dev
30 comments fedilink hide all child comments
 

I am a senior java developer in the cloud/distributed arch/ microservice area.

I've touched on golang in the past, but not learnt it in any formal/extensive way.

I see it cropping up in many java/microservice positions, and I'm curious if this is at some point going to overtake java in my area.

The current benchmarks seem to suggest that if autoscaling is key to your services, golang is the way to, well, go.

I looked at the job market and it doesn't yet seem to have taken over, but I'm curious how this is likely to play out over the next decade and if quakus for example is likely to become more competitive against golang. Interestingly, golang specific roles on average pay less than java ones in my area.

Let me know your thoughts or if you have any good articles / content on the subject.

you are viewing a single comment's thread
view the rest of the comments
[–] Ephera@lemmy.ml 2 points 5 days ago

My impression has been that it's not a good language. That relatively many people try it out, because the initial learning curve is small, only to fall out of love with it hard a few months later, because the low language complexity results in high complexity of each individual codebase.
Perhaps the most elaborate rant about that experience: https://fasterthanli.me/articles/i-want-off-mr-golangs-wild-ride

And yeah, personally I care a lot about being able to work with good tooling, so that's my reason to stay away from it as long as I don't need it for employment.

But our industry famously loves terrible languages (see JavaScript, Python, PHP etc.), so if you are just interested in employability, I do imagine that you will continue to find jobs a few years from now. I certainly also feel like it's well established in ops tooling and cloud services, so there's gonna be people who continue to write new software with golang in those fields.