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?

>>39
Yes, a variable, by definition, cannot vary. When you write an equation like x - 1 = ln x, it will only have meaning if the second x is exactly the same as the first x.
In fact, imperative languages have variables too - the function arguments. The imperativists' error is that the other things they call variables - like local or global assignables - are not variables at all because they are mutable and a variable is immutable. Like, by definition.

>>40
Variables don't vary because they are unknown consts. Which you would know if you had even school-level mathematical education. But no, you chose to be a coder, and coders don't need all this mathematical bullshit, do they?

>>41
Variable literally means 'able to vary'. And in most imperative languages, an equation like you wrote wouldn't be valid except in a condiational statement. There's basically three meanings of the = sign. In math, it is creating a constraint, STATING THAT the two sides are equal. In programming, it is either used as a test (ASKING IF the two sides are equal), or as assignment (indicating a change of state). The assignment statement has restrictions compared to the other uses, namely the left-hand side must be an object, not an expression or literal value. It is inherently directional, as left = right means "set left to the value of right". Mathematical equality is declarative, not imperative. X = Y is just saying that a constraint must be met, not how that constraint should be met if X and Y are not currently equal. Imperative programming requires defining a dependent variable, which cannot always be determined by looking at an equation.

>>43
Your opinions on syntax are absolute rubbish. I'll let you check you my dubs anyway.

>>43

Variable literally means 'able to vary'

But not between instances of itself. I.e. in any equation/proof/term all instances of a variable must be strictly equal. No variability at all. If it varies, it's not a variable but a mutable assignable.

And in most imperative languages

So you are completely mathematically ignorant, right? Don't even know what an equation is? Why don't you go sweep the streets, you imperative ignoramus?

>>45
It can vary over time, instances are irrelevant. A variable is a designated area of RAM (or possibly a register, IO port, or whatever), it can only hold one value at any given time.

>>46
Only if you're an idiot.

A variable is a designated area of RAM

Variables have nothing to do with RAM. I already told you that imperative languages have one example of a variable - the function parameters, but you couldn't even understand that. Or maybe you are numbskull enough to believe that function parameters are pieces of memory. Either way, off to sweep the streets and take out people's trash you go, ignoramus. You have no place anywhere near a compiler.

Perhaps "unknown const" is the best idea of a variable that an imperative ape can have.

Like, it's immutable, you know. But we don't actually know it. Could be anything, as long as it's this type, right? Like, you diggin what I'm telling you, bruh? So a variable is a const, you gettin that, dawg? A const. Yes. Like, it doesn't vary the way usual assignables vary, right? It's a const. But it varies because we, like, can substitute any const in its place. Cuz it's unknown and shit? So yeah, like a const but we don't know it. But still unknown. So, uh now you've been redpilled as far as these things called variables go, yeah, gimme a high five bruh!

>>47
Sorry, I didn't read your previous posts.