The thread's a bit old, but I'll reply anyways. > Scala, Ceylon, Clojure provide their own stdlibs. On top of the JVM ones when targeting the JVM. E.g. java.l

The thread's a bit old, but I'll reply anyways. > Scala, Ceylon, Clojure provide their own stdlibs. On top of the JVM ones when targeting the JVM. E.g. java.lang.String (Kotlin too) > You can write non-OOP programs in Java bytecode Everything is still an object and all code is in methods. There is no way around that. Also, there are many other things like forced GC and what not that marry the bytecode to certain paradigms. > it's about ensuring that if someone claims they run Java bytecode, they actually can run it. And about their impls of java.lang and other base packages. And a way to make sure that licenses that Oracle doesn't like, such as non-OpenJDK-derived open source stdlib impls, are not given the tests. Other languages with compat tests publish them for all and yet aren't worried about losing their name. This is dangerous reasoning to apply to keeping things opaque. It isn't just those big companies implementing WASM. I implemented a WASM backend for the JVM [0]. The core test suite, which I use and comply with 100%, is available to all [1]. 0 - https://github.com/cretz/asmble/ https://github.com/cretz/asmble/ 1 - https://github.com/WebAssembly/spec/tree/master/test https://github.com/WebAssembly/spec/tree/master/test