Why Go can lower GC pauses to sub 1ms and JVM has not?

Question

So there\'s that: https://groups.google.com/forum/?fromgroups#!topic/golang-dev/Ab1sFeoZg_8:

Today I submitted changes to the garbage collector that m

Answer 1

What are the (architectural?) constraints which prevent JVM from lowering GC pauses to Go levels, but are not affecting Go?

Principal I would say is that java is reference-oriented language, while Go is value-oriented language.

There are many aspects of it, Object metadata, Concurrency Handling... Naturally Java doesn't allow to put primitives in collections which give a lot of overhead in a sense of amount of Objects, in Golang you have Array, Slice and Map which support primitive types...

Here is a good article about Golang GC development and evolution.