TeaVM – Ahead-of-time transpiler of Java bytecode to JavaScript or WebAssembly

Post by bdamm » Fri, Jan 05, 2018, 7:14 AM UTC

pjmlp wrote: post #21

kodablah wrote: post #4

For the reverse, I wrote a WASM-to-JVM compiler: https://github.com/cretz/asmble . I think WASM has the ability for us to finally cross the language boundaries without marrying ourselves to C/C++ ABI. But at this early stage, there's no common stdlib for all languages to share.

> I think WASM has the ability for us to finally cross the language boundaries without marrying ourselves to C/C++ ABI That is how many maninframes work, and the original idea behind the CLR.

Post by tracker1 » Fri, Jan 05, 2018, 7:24 AM UTC

pjmlp wrote: post #38

frik wrote: post #34

The last thing we need in hindsight to Meltdown and Spectre is running untrusted binaries in the browser aka WebAssembly. Btw deactivating WebAssembly support in Chrome 63 (up-to-date) doesn't work anymore!! chrome://flags/#enable-webassembly Setting it to "deactivated" does nothing, WebAssembly is still active.

I keep saying that WebAssembly is the revenge of Flash, Applets, Silverlight, ActiveX,... Just wait until it gets a bit more mature. It will be the same fun as when Ads moved away from Flash into HTML 5/JavaScript.

Post by abiox » Fri, Jan 05, 2018, 7:33 AM UTC

doug1001 wrote: post #11

burke wrote: post #9

Earlier quoted context omitted.

I get that we've lost this battle, and some people seem to think there's a useful distinction being made, but man, does the word 'transpile' grate on me.

thank you; some consolation to know it's not just me does this seems like another instance of the annoying practice in our field of someone giving a name to a thing because they think it's new, though it's not (ie, source-to-source compilers have been around as long as source-to-bytecode compilers)--no need to re-name them wish they would just stop it and get the hell off my lawn

Post by abiox » Fri, Jan 05, 2018, 7:44 AM UTC

burke wrote: post #9

ant6n wrote: post #3

Compile

I get that we've lost this battle, and some people seem to think there's a useful distinction being made, but man, does the word 'transpile' grate on me.

Post by sitkack » Fri, Jan 05, 2018, 7:50 AM UTC

earenndil wrote: post #35

kodablah wrote: post #4

For the reverse, I wrote a WASM-to-JVM compiler: https://github.com/cretz/asmble . I think WASM has the ability for us to finally cross the language boundaries without marrying ourselves to C/C++ ABI. But at this early stage, there's no common stdlib for all languages to share.

> I think WASM has the ability for us to finally cross the language boundaries without marrying ourselves to C/C++ ABI Uhhhhh. This sounds like a kind of silly thing to say, when you just described the jvm. Except for the part where there is a common stdlib.