News for hackers. Stuff that matters.

A comment on Go’s march to low-latency GC. Parent comment

Re:Go’s march to low-latency GC by zamalek on Thursday July 07, 2016 @01:59PM (#12051019)
Disclaimer: despite all my praises for Go, I don't actually use it for real problems. Would I like to use Go? Definitely! Is there a problem that I'm trying to solve that needs Go? Certainly not. In many cases I'd objectively pick Rust over Go, but when it comes to threading primitives, Go is somewhat unmatched.

> pick my battles

Exactly my point. A good coder will choose the tool that expresses the solution correctly. C is a very good choice, it always will be, there are sometimes better choices. Ultimately it seems as though we are in agreement; cheers!

[ Parent | on HN ]
Re:Go’s march to low-latency GC by DanWaterworth on Friday July 08, 2016 @03:27AM (#12054044)
Go's threading primitives are not unmatched. You can do the same in Rust [1], but the gold standard in my eyes is STM in Haskell which allows you to block on arbitrary conditions.

[1] https://doc.rust-lang.org/std/macro.select!.html#examples

[ Parent | on HN ]