zlacker

[return to "Go is still not good"]
1. the_du+yd[view] [source] 2025-08-22 11:46:04
>>ustad+(OP)
I personally don't like Go, and it has many shortcomings, but there is a reason it is popular regardless:

Go is a reasonably performant language that makes it pretty straightforward to write reliable, highly concurrent services that don't rely on heavy multithreading - all thanks to the goroutine model.

There really was no other reasonably popular, static, compiled language around when Google came out.

And there still barely is - the only real competitor that sits in a similar space is Java with the new virtual threads.

Languages with async/await promise something similar, but in practice are burdened with a lot of complexity (avoiding blocking in async tasks, function colouring, ...)

I'm not counting Erlang here, because it is a very different type of language...

So I'd say Go is popular despite the myriad of shortcomings, thanks to goroutines and the Google project street cred.

◧◩
2. zwnow+de[view] [source] 2025-08-22 11:50:15
>>the_du+yd
What modern language is a better fit for new projects in your opinion?
◧◩◪
3. alouki+re[view] [source] 2025-08-22 11:52:21
>>zwnow+de
Elixir, with types
◧◩◪◨
4. sarche+rg[view] [source] 2025-08-22 12:07:10
>>alouki+re
That doesn’t exist yet. Also Elixir is in no way a replacement for Go.

It can’t match it for performance. There’s no mutable array, almost everything is a linked list, and message passing is the only way to share data.

I primarily use Elixir in my day job, but I just had to write high performance tool for data migration and I used Go for that.

[go to top]