All right, do let's get this straight: - This is from MongoDB, which, in my book, is already a not-so-reputable organisation (ref. to Jepsen et. al.) - The wh

All right, do let's get this straight: - This is from MongoDB, which, in my book, is already a not-so-reputable organisation (ref. to Jepsen et. al.) - The whole thing about Golang is basically a paragraph that puts a parallel between Java and Golang. I'm not an expert in Go, but I've dabbled in both quite extensively. From a programming point of view, Go is better in that it requires WAAAAAAAAAY less boilerplate. Want an HTTP server ? Already in the stdlib. Want to do OAuth ? Already in the stdlib. From a systems administrator's point of view, I do not need to worry AT ALL, about whether this version of JVM, or that parameter to have the GC not pause too much (although ZGC and the new bunch looks amazing), I just have a single (albeit so heavy) executable, I put it on the server, and it just works. And that's the beauty of it IMHO. I don't think they're comparable. Maybe for software where you just want to send off some UML to people in India, Java is probably the way to go. But if you wanna write software fast, and deploy it fast, and have some static analysis bundled in, then Go is miles ahead of Java IMO.