Errata for Java RAMBO Manifesto

Earn beer money! If you spot an error, send it my way. Each technical error earns $5. Grammar errors may earn an award, but they're harder to define and so I'm not making guarantees. I reserve the right to decide what constitutes an error and the right to award multiple prizes in the case of a tie. 
 

Errors:


David Jamburia writes:
 

The FAQ asks, “Aren’t all objects kept in RAM?” and answers, “Well, yes.” That is too absolute for Java/JVM behavior. 
The JVM specification defines the heap as the runtime data area from which class instances and arrays are allocated, but it does not require that heap storage correspond to physical RAM. More directly, Oracle’s HotSpot documentation says escape analysis can make an object “scalar replaceable” and eliminate that object’s allocation from generated code entirely. 
A technically safer wording would be along the lines of: live Java objects are conceptually represented in the JVM’s runtime memory model, typically using heap storage, but the JVM does not guarantee physical-RAM residence and an optimizing JVM may eliminate some allocations entirely. 

This is certainly a fair point. I'll note that some have worked out ways to pin the JVM heap into RAM with small C wrappers that use mlock, but it's a bit of a kludge and seems to go against the spirit of the mantra of write once, run anywhere.