Yup... I've seen a lot of java code aiming at high-performance that does awkward/ugly things (e.g., class-static objects which are actually constantly-reused te

Yup... I've seen a lot of java code aiming at high-performance that does awkward/ugly things (e.g., class-static objects which are actually constantly-reused temporary objects, manually-managed temporary object pools, etc) to avoid heap-allocation, in cases where C++ code would simply use its very natural stack-allocation.