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. jiehon+rU1[view] [source] 2025-08-22 21:08:04
>>zwnow+de
Maybe weirdly I’d put swift in there.
◧◩◪◨
4. vips7L+SZ1[view] [source] 2025-08-22 21:40:58
>>jiehon+rU1
Swift is my hope for the next big server language. Great type system, great error handling.
◧◩◪◨⬒
5. Degora+Bw3[view] [source] 2025-08-23 14:00:27
>>vips7L+SZ1
In my opinion they need to invest a lot more time and money into it for that. The development experience on VSCode was pretty bad (I think the LSP has a memory leak), and some important (for me) libraries aren't tuned very well yet (a Vapor webserver can sit around 100 MiB memory, whereas putting a bunch of load on the grpc implementation balloons the memory usage to >1 GiB).
[go to top]