News for hackers. Stuff that matters.
Re:Application data caching using SSDs by gshulegaard on Wednesday May 25, 2016 @03:27PM (#11772398)
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.

Re:Application data caching using SSDs by geodel on Wednesday May 25, 2016 @03:39PM (#11772473)
If you check this link: 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.

Re:Application data caching using SSDs by igouy on Wednesday May 25, 2016 @09:43PM (#11774635)
Re:Application data caching using SSDs by igouy on Thursday May 26, 2016 @12:31PM (#11779274)
Re:Application data caching using SSDs by gohrt on Wednesday May 25, 2016 @04:04PM (#11772665)
Re:Application data caching using SSDs by gshulegaard on Thursday May 26, 2016 @01:55PM (#11780076)
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

Although there are still additional challenges with parallel vs. simple concurrent programming.