3 ms·

I think the bigger thing is the deliberate design of go for parallel processing. I feel like the Go GC is still an issue, although getting better every day, bu

I think the bigger thing is the deliberate design of go for parallel processing. I feel like the Go GC is still an issue, although getting better every day, but the benefits in regards to "handling tens of thousands of client connections" potentially make the GC easier to swallow than Java. But that's is just my outside looking in take on it.

geodel 10y ago
If you check this link: http://benchmarksgame.alioth.debian.org/u64q/go.html http://benchmarksgame.alioth.debian.org/u64q/go.html Java uses about 2-10 times more memory most of time compare to Go. So I'd think Java's GC has to be at least 10 times better/sophisticated than Go's. Though I doubt if it is really 10 times better.
- igouy 10y ago
  >more memory most of time< http://programmers.stackexchange.com/questions/189542/ http://programmers.stackexchange.com/questions/189542/
  - igouy 10y ago
    Specifically: http://programmers.stackexchange.com/a/189552 http://programmers.stackexchange.com/a/189552
gohrt 10y ago
https://blog.golang.org/concurrency-is-not-parallelism https://blog.golang.org/concurrency-is-not-parallelism
- gshulegaard 10y ago
  As a Python programmer, I am intimately familiar with the distinction between concurrency (Coroutines) and Parallelism...and additionally the difference between multi-threaded and multi-processing within Parallelism. It was my understanding that Go's center around concurrency made parallelism also easier to approach than most languages: https://golang.org/doc/effective_go.html#parallel https://golang.org/doc/effective_go.html#parallel Although there are still additional challenges with parallel vs. simple concurrent programming.