Post #2702284
2026-03-19 13:07 UTC
A few reasons:
- Less environment related friction
- Fewer conflicts with my setup
On macOS, and especially with Fish shell, Python workflows have been more fragile than I would like. Go has generally felt much more straightforward.
- Much easier to run through agents and automation
If a tool can be compiled and executed cleanly without extra setup steps, it is already winning. Go fits that model far better for me.
2/3
Replies (1)
-
@funkyidol@androiddev.social 2026-03-19 13:07
I am definitely noticing a shift, Go is becoming my first instinct for a lot of general scripting work. I will write a more detailed blog on this soon, including: - where Go has been a better fit for me - where Python still clearly wins - and some of the small tools I want to build in Go next Curious if others have felt the same shift, especially if you work on macOS or rely heavily on automation/agent workflows. #golang #python #softwareengineering #automation #developertools #cli 3/3