Finance and video games both have really stubborn engineering traditions. > https://openjdk.org/jeps/442 https://openjdk.org/jeps/442 This succinctly is the a

Finance and video games both have really stubborn engineering traditions. > https://openjdk.org/jeps/442 https://openjdk.org/jeps/442 This succinctly is the answer. > not every `new Foo` actually results in a heap allocation, and can be optimised to work directly in registers. While I know in my heart of hearts that you are right, this category of advice has so many caveats. It's like when Graal markets itself as a potential substitute for NodeJs, where its performance is abjectly terrible. I have never personally succeeded in convincing anyone with these deep programming traditions to try something new that may be Better in Every Way. It always has to be this long, trickle down journey of adoption. People still talk about John Carmack and video game engineering, decades after any of his innovations have been verbatim relevant and decades after an individual could possibly have a hope and prayer of authoring a first person shooter with an audience from scratch. But see, I need to know a lot of stuff to understand that.