4 ms·
> The JVM's type system has been proven correct. I'm not sure which proof you are referring to, but the Java and Scala languages both have unsafe type systems:
by titzer 9y ago
> The JVM's type system has been proven correct.
I'm not sure which proof you are referring to, but the Java and Scala languages both have unsafe type systems:
https://2016.splashcon.org/event/splash-2016-oopsla-java-and-scala-s-type-systems-are-unsound-the-existential-crisis-of-null-pointers https://2016.splashcon.org/event/splash-2016-oopsla-java-and...
(Admittedly this is due to parametric types which are erased).
The JVM bytecode verification algorithm is over 100 pages in the spec.
> E.g. Chrome might add new opcodes or APIs that rely on other Chrome-only features.
We aren't doing that currently. We plan to continue participating in the W3C processes which have worked well over the past 2+ years.
- mike_hearn 9y agoI'm talking about the JVM type system, not Java's. They're not quite the same due to generics erasure and a few other things. We aren't doing that currently All browser makers have long histories of forking the platform with proprietary extensions more or less whenever they feel like it. So what does this assurance mean? Indeed that's now how HTML5 is meant to evolve! Nobody even uses the W3C anymore do they? It's all just throwing whatever extensions get built by browser makers into HTML5. I'm sure WebAssembly will have its share of compatibility matrices and vendor-prefix equivalents soon enough.