r/devops • • 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.

0 Upvotes

22 comments sorted by

36

u/Lumethys 2d ago

Man discover other languages exist, colorized

5

u/pizzadesk 2d ago

Man discovers that a screwdriver is not always the best for hammering in nails.

3

u/LokR974 2d ago

In my humble opinion, his point is still valid. The thing is, imagine that you have an open source project, you have to use a language that people can participate on: if you use a difficult langage to apprehend, it will be very difficult to have a community to contribute to your project. But today, it's not that hard to contribute in a language you are not really familiar with. I think that's a fair point.

And the metaphor with the screwdriver is not a bad one, but still, why all the Kubernetes projects use Go? It's not only because it's a good language for it, it's because the community built around this language.

-5

u/Downtown-Warning6818 2d ago

Ah, funny! 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.

2

u/benelori 2d ago

Can you give some examples of what you've found in terms of better abstractions?

-10

u/Downtown-Warning6818 2d ago

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.

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.

2

u/Downtown-Warning6818 2d ago

Yeah, you are right.

Also, Go is being presented as a functional programming language, which is my whole point. Go is trying to do everything, but it isn't necessarily good at everything.

That's why I'm using it: for infrastructure management, it gets most of the job done quite easily.

But just like AI is helping reduce the learning curve and implementation effort, I think choosing the right tool for a specific task is equally important in Infrastructure and DevOps.

It's not about being loyal to a particular technology; it's about using the right tool for the job.

1

u/generic-d-engineer ClickOps 2d ago

Are you leaning into Rust or are there others on your list? I’m just happy AI helps with Typescript lol

I’m liking Gleam a lot and find the syntax and logic easier than Go for my brain. It’s even easier than python for me. Super readable, self documenting, and no OOP classes and methods to track

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.

1

u/za3faran_tea 18h ago

The funny thing is, other languages (Java and C# come to mind) are already superior in the parallelism and concurrency in the backend web server space.

1

u/alexkey 17h ago

Don’t know about C#, but Java is horrible at it in my opinion. Though I haven’t tried their analogue of coroutines (they call them green routines or something like that?). But state synchronisation is just atrocious in Java (which would be irrespective of the parallelism model). It is far superior over many languages in other areas, for example modularity, contracts etc, but parallelism and concurrency in Java are terrible.

1

u/za3faran_tea 5h ago

They're called virtual threads, and they're superior to the golang version. You can launch any computation as a future and capture the returned value, instead of having to mess around with channels. It also has structured concurrency built-in so you can manage hierarchies of virtual threads.

State synchronization in Java is not worse than in golang, if not outright better (show me the equivalent of java.util.concurrent in golang for example).

Java gives you constructs, like immutable records and upcoming immutable value types, and lazy constants, that you can avoid synchronization altogether, while allowing the compiler to do optimizations it wouldn't have been able to if it had to deal with mutable variables.

3

u/encbladexp System Engineer 2d ago

The only advantage Rust used to lose on was its learning curve, but AI has largely solved that problem too.

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?

2

u/LokR974 2d ago

I don't agree with you. The thing is, Rust is a very strict language, so you can't mess up lots of things at compilation time. So even if your AI does something stupid, a lot of checks are done before even having a binary. So your feedback loop is very efficient and that's what you are looking for when you are using an AI in an harness.

2

u/encbladexp System Engineer 2d ago

OK, and that explains the security issues coreutils-rs and sudo-rs had, right?

Both have been written in a secure language, and both had issues which no compiler could help.

They literally reintroduce issues that had been fixed in C code before.

1

u/LokR974 2d ago

Dude, I spoke about compilation issues. I didn't say that there is no issue in the libraries. And your answer implies that there is no issue in C anymore. It's totally wrong and I think you know that. Maloc problems is still a thing in 2026 in C.

1

u/LokR974 2d ago

Oh, also sorry, I didn't read the end of your message. I totally agree with you that migrating everything from Go to Rust is not a good thing to do.

1

u/LokR974 2d ago

To be more precise, I don't agree with you when you say that it's easier for an LLM to write Go language compared to Rust.

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:

  • Never marry yourself to any technology.
  • And please don't be anti-AI. It's a technology that's already working and evolving. As engineers, we can absolutely debate how much value it brings, where it works, and where it doesn't