←back to thread

Go is still not good

(blog.habets.se)
644 points ustad | 3 comments | 22 Aug 25 09:25 UTC | HN request time: 0s | source
Show context
bitdeep ◴[22 Aug 25 19:50 UTC] No.44989021[source]▶
- I’ve seen a lot of debate here comparing Go’s issues (like nil handling or error scoping) to Rust’s strengths.

- As someone who’s worked with C/C++ and Fortran, I think all these languages have their own challenges—Go’s simplicity trades off against Rust’s safety guarantees, for example.

- Could someone share a real-world example where Go’s design caused a production issue that Rust or another language would’ve avoided?

- I’m curious how these trade-offs play out in practice.

Sorry, I don't do Go/Rust coding, still on C/C++/Fotran.

replies(1): >>44989722 #
1. metaltyphoon ◴[22 Aug 25 20:57 UTC] No.44989722[source]▶
> Go’s design caused a production issue

A simple one, if you create two separate library in Go and try to link with an application, you will have a terrible time.

I've ran into this same issue: https://github.com/golang/go/issues/65050

https://www.youtube.com/watch?v=xuv9A7CJF54&t=440s

replies(1): >>44992018 #
2. pensatoio ◴[23 Aug 25 01:16 UTC] No.44992018[source]▶
> caused a production issue

that's not a production issue, and it's a very niche use case

replies(1): >>44992230 #
3. metaltyphoon ◴[23 Aug 25 01:47 UTC] No.44992230[source]▶
It's a niche use case to have software that load plugins and it just so happens those plugins are written in Go? No it's not a niche case. If all programing you do in Go is web servers than sure you won't see this.