3 ms·
Generally speaking it's the data associated with the calls that is risky, not the bytecode itself. The way the JVM works is by having specific permission check
by nl 12y ago
Generally speaking it's the data associated with the calls that is risky, not the bytecode itself.
The way the JVM works is by having specific permission checks at points within the code, and they are enforced by the JVM. I think the CLR works in a similar fashion.
You can run Python on top of the JVM and take advantage of this, but I think the version of Python (JYthon) is pretty old.