I really enjoyed using Go in my Distributed Systems course in college, and I've enjoyed using it as a replacement for Python for little scripts I've written since the typed aspect of it makes it easier for me to go back and read what I've done. But, I have not enjoyed the Go micro service we use at work. We went with Go thinking the coroutine thread implementation would significantly improve performance over a Java m…
> but the service turned out to be GC limited Go indeed has a lousy GC (compared to the JVM, at least.) This is why, in most production Go codebases I've seen, there's heavy reliance on https://golang.org/src/sync/pool.go (or a NIH knocked-together version of it, if the author doesn't realize sync/pool exists.) Try just switching a few of your most-oft-called constructors to allocate from a pool. It's pretty much the…
Re: Show HN: My notes on Working with Go
#91Right, but if we go with Rust we won’t have to worry about GC issues