Re:Go generics are not bad
by germandiago on Saturday July 09, 2022 @04:56AM
(#32033213)
Well, for latency you do have to deal with the GC very carefully, but the investment/ratio in Go is very good. It is just not for absolutely every use case, like everything else in your toolbox.
[ Parent
| on HN ]
Investment ratio in Go is only good because of how little you have to invest. In Rust the required investment is bigger, but you get a lot more in return. Not sure about which ratio is really better.
GC is only a minor reason I chose Rust over Go for a networking related project. Despite having a GC, Go definitely feels more low-level and less structured than Rust, and leads to code that is longer and harder to reason about.
It is very similar to how a language with only a goto instruction to do control flow would be definitely simpler/smaller than a language that supports functions, loops and conditions, but the actual programs written in it would be brittle and harder to understand.
Re:Go generics are not bad
by germandiago on Saturday July 09, 2022 @03:48PM
(#32038627)
> Not sure about which ratio is really better.
That is going to depend entirely on requirements. Fast delivery, fast execution, correctness and others. No tool for everything :)