Menu

Go is going I think

Reading 0:00
15s threshold

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.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.