4 ms·
That's definitely such an underspecified claim that it's not even wrong. Fast as C under what conditions? I've personally found that a lot of Go's marketing is
by Felz 8y ago
That's definitely such an underspecified claim that it's not even wrong. Fast as C under what conditions?
I've personally found that a lot of Go's marketing is, if not misleading, outright false. As an example: https://blog.plan99.net/modern-garbage-collection-911ef4f8bd8e https://blog.plan99.net/modern-garbage-collection-911ef4f8bd...
- Thaxll 8y agoIf you were to use Go you would know that the GC is indeed pretty fast, on part or faster than Java / C# in many scenarios.
- Felz 8y agoThat's exactly what the article I linked said, isn't it? It has low pause times, at the expense of everything else. Beware trading a visible cost for an unbounded number of smaller costs. In Go's case, in return for minimal pausing you get memory fragmentation, terrible performance if the GC is ever seriously taxed, and a 100% (!) heap memory use overhead. If you're just writing commandline daemons or servers you restart every ten minutes though, who cares? Go doesn't come off too badly in this because it's not Java, which allocates like crazy. That's a laudable tradeoff, but that does not mean they solved garbage collection very well.