this post was submitted on 31 Jul 2025
36 points (95.0% liked)
Programming
22019 readers
377 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I used to work in Java and now work in Go writing backend services. I think I enjoy writing Go more than I did Java most of the time.
Do you have any info on the architectural reasoning behind making the switch?
My reading suggests that in an area where autoscaling is key, Go is one of the best right now due to its performance from a cold starts.
I was hoping I'd get more answers of people discussing this type of requirement to be honest - the replies so far are having me second guess my research.
I switched companies. I started go when replacing php at a previous company. I wanted to do rust at the time, but my options from the CTO were go or newer php (we were 5.x IIRC). I chose go.
My current company decided on go before I started. There's some python ml stuff and some other things in functional languages, but we're primarily go. I don't know why specifically it was chosen. The old codebase was a bit of go and the original legacy in Ruby. I'm definitely glad they decided to move away from Ruby slowly (and compleltely in the new codebase).