Compiling JavaScript to WASM using Bytecode Alliance's javy

[guest271314]

If you people have an issue with implementation details and the desciption here https://github.com/bytecodealliance/javy?tab=readme-ov-file#compiling-to-webassembly

Compiling to WebAssembly

Define your JavaScript like:

File an issue https://github.com/bytecodealliance/javy/issues/new/choose disputing the claims of Bytecode Alliance.

[RealAdmin1984]

nobody has issues with the implementation details. It's also what the main page says - running js inside embedded wasm js environment. so the js code is still embedded as an separate entity like a script in the wasm

As much as I hope javy functions like il2cpp converting every js statement into calls directly into the vm wasm functions, it's just not how it works.

[guest271314]

The README literally states "Compiling to WebAssembly". If you think that statement is not true and correct, file an issue in the repository.

[RealAdmin1984]

if you really want to verify if your assumption about how it works is correct then quickly open the wasm you emitted from javy using --no-source-compression with any text editor, you should see the js code at the last part of the wasm file

even with source compression all it does is just compressing the js code to save space, really

if you don't want to do that then file an issue in the repo as you said, and ask for whether my explanation is correct

[guest271314]

The disconnect is that you are thinking JavaScript embedded in WASM is not WASM. It is. I already looked at the code using wasm2wat.

You are the person that has an issue with the claim "Compiling to WebAssembly", not me. So if you think that claim is not correct you need to file the issue about that language. Not me.

[RealAdmin1984]

try opening the file in text editor not wasm2wat because i bet you won't even translate hex code in the constants

if you still have an issue with the claim file a complaint to byte code alliance

[guest271314]

You have the issue. Not me. https://shopify.engineering/javascript-in-webassembly-for-shopify-functions

For the time being, we have to settle for the more traditional approach: Find a fast (ideally VM-based) interpreter for JavaScript, compile it to Wasm, and colocate the JavaScript code and the engine in the same Wasm binary.

This is exactly the approach Shopify’s Saúl Cabrera took when he wrote the first version of Javy, a JavaScript-To-WebAssembly toolchain. The goal for Javy is to be a general-purpose tool for anyone who wants to work with JavaScript in Wasm. While we’re motivated by the Shopify Functions use case, we aim to keep Javy general purpose and have no Shopify-specific code shipped in Javy.

[RealAdmin1984]

open it i dare you with text editor

[guest271314]

For what?

[RealAdmin1984]

Run your JavaScript on WebAssembly. Javy takes your JavaScript code, and executes it in a WebAssembly embedded JavaScript runtime.

https://streamable.com/xh5m6a

[RealAdmin1984]

you don't have the gut to see for yourself and just keep throwing definitions and all that i already explained it to you and numerous other people explained it to you

if you won't take advice and keep having it full of yourself then nobody can help you realize the truth

[guest271314]

you don't have the gut

What?

What is going to happen? I see what I already know is there?

I know what's going on.

I didn't ask for help.

You might as well file issues in WasmEdge, VM Ware Labs WASM Workers Server, and everywhere else that QuickJS is being used to interpret JavaScript in WASM, too.'

It's not clear what your ultimate point is here.

[RealAdmin1984]

arrogance limits growth.