Why is the Java GC so garbage?

It is 2016, why does Java still shit itself like a baby if you try to serve a non-toy amount of traffic with it without tuning your garbage collector settings yourself like some sort of caveman?

Is it so hard to set defaults that don't randomly freeze like a deer caught in the headlights at the sight of multiple qps?

>>10
Listen up, you stupid fuck. If you're allocating/freeing all over in C that'll add a ton of slow overhead to your program. You need to buy a proper GC for $$$ or make sure not to heap allocate any objects ever. GC is just as fast/slow as explicit memory management, because you underestimate how shit slow the heap is in other languages. If memory management overhead is a problem in any language, you have to do the avoid allocation dance.

Now, go kill yourself.

>>13
If you don't understand the situations in which your runtime can decide to stack allocate, you do not deserve to attempt programming. Again, your suicide is overdue. Get on it.