Sure. I guess I'd point out that even when the long lifecycle, the optimization on live paths happens quick. It doesn't take too many invocations before the jvm optimizes.

That's similar to how js does things.

Java does have a "client" optimization mode for more short lived operations (like guis for example) and AFAIK it's basically unused at this point. The more aggressive "server" optimizations are faster than ever and get triggered pretty aggressively now. The nature of the jvm is also changing. With fast scaling and containerization, a slow start and long warmup aren't good. That's why part of the jdk dev has been dedicated to resolve that.