Re:Program your next server in Go
by asolove on Tuesday June 07, 2016 @02:18PM
(#11856477)
Presumably he is complaining about the GC implementation's characteristics, not its existence. You can read a description of the team's design decisions here: https://blog.golang.org/go15gc but a simple summary would be: memory is cheap and getting cheaper, so focus on making GC fast rather than small memory footprints.
[ Parent
| on HN ]
Hasn't go been improving the GC with it's rounds of updates to the language?
Re:Program your next server in Go
by kasey_junk on Tuesday June 07, 2016 @02:28PM
(#11856583)
Yes, with an emphasis on speed not memory.
actually thats what the Java G1GC (which will be the default in Java 9) does aswell.
However I would still favor java instead of go
Re:Program your next server in Go
by nameless912 on Tuesday June 07, 2016 @02:31PM
(#11856608)
And in my opinion, this is a great tradeoff. Ultimately, adding more RAM to a server (or clicking a button on the AWS console) is a very easy fix. However, reducing latency is almost never easy. If they can prevent GC stuttering, I'll take the higher memory overhead every time.