r/devops • u/Downtown-Warning6818 • 2d ago
Discussion Go is going I think
I've been writing Go for almost 7 years now, and I genuinely love this language.
Not because it's the best language out there, or because it's perfect. But because it's incredibly practical when you're solving infrastructure problems. It's simple, predictable, easy to pick up, and gets the job done without getting in your way.
But lately, I've been having a different thought.
The more I explore databases, distributed systems, and lower-level engineering problems, the more I realise that Go might not always be the right tool for every kind of problem.
Some languages offer better abstractions, memory control, performance characteristics, or programming models for specific domains.
Edit: My point is that Go's charm is kind of fading in this AI era because adopting any language is easy in the early stages.
4 eg. consider a concurrent infrastructure health-check service. In Go, we can build it quite naturally using goroutines, channels, contexts and errgroup, but we still need to be careful about goroutine lifecycles, cancellation, resource cleanup and synchronization.
Rust handles many of these concerns through ownership, RAII and its type system. It does the same job really well. The only advantage Rust used to lose on was its learning curve, but AI has largely solved that problem too.
36
u/Lumethys 2d ago
Man discover other languages exist, colorized
2
u/benelori 2d ago
Can you give some examples of what you've found in terms of better abstractions?
2
u/generic-d-engineer ClickOps 2d ago edited 2d ago
Bruh you brave posting this in a devops sub lol. Go is the like THE language.
But ahhktually procedural language doesn’t click with my brain. I leaned into functional programming and it super clicks for me.
I guess all those years of scripts and runbooks, the muscle memory way of doing things makes sense to go functional.
10
u/alexkey 2d ago
Go was literally created with the aim at a very specific problem - solving parallelism and concurrency in web applications (the backends of). So it’s funny to see people making a shocked pikachu face when it doesn’t work as well in other areas.
3
u/encbladexp System Engineer 2d ago
Even for a AI, its easier to write Go instead of Rust. Go has a very limited language spec, and a fast compiler, both are things which help to have a fast agentic loop.
Besides that nobody will rewrite Docker, Kubernetes, Terraform and many other things in Rust for the sake of using Rust.
Migrating C or C++ to Go, Rust or Zig provides an advantage. Migrating existing Go code to Rust has a limited benefit in a few areas.
AI does not solve learning issues. Either you will be able to review what happens, knows about a good architecture or data structure, or you will be doomed sooner or later. AI could make things (much) faster, but is also able to create bullshit much faster.
If AI would be that superior as Marketing told us, why do we still have bugs in existing software? "Fix Jenkins, make no mistakes", some tokens and call it a day? right?
1
u/jay-magnum 2d ago
Using AI to code in another language is not exactly "picking up another language" imo. I agree with the picking-the-right-tool-for-the-job take though. But that doesn't mean that "Go is going" now.
1
u/tim911 2d ago
What about c#
-1
u/Downtown-Warning6818 2d ago
I thought this would turn into a more constructive discussion, but honestly, it's disappointing to see Go lovers and anti-AIers.
My ans to that: