> Because the security manager needs to be able to introspect the stack. Not allowing certain “optimizations” in security-sensitive contexts is perfectly fine.

> Because the security manager needs to be able to introspect the stack. Not allowing certain “optimizations” in security-sensitive contexts is perfectly fine. In fact, this is exactly what Avian, the CLR (and pretty much everyone else) is doing. > Avian isn't a JVM; it's "designed to provide a useful subset of Java's features" and can run some Java code. Now you're talking about legal aspects. Frankly, I'm not interested in discussing those. Avian is a JVM for all practical purposes. If you disagree, please provide a test-case which runs on HotSpot but not on Avian.