wabt

WASM: WebAssembly > Specification > Wasm program > Code representation > C source code and corresponding WebAssembly https://en.wikipedia.org/wiki/WebAssembly#Code_representatio... WASI: https://en.wikipedia.org/wiki/WebAssembly : > WebAssembly System Interface (WASI) is a simple interface (ABI and API) designed by Mozilla intended to be portable to any platform.[84] It provides POSIX-like features like file I/O constrained by capability-based security.[85][86] There are also a few other proposed ABI/APIs.[87][88] [88]: webassembly/wasm-c-api: https://github.com/WebAssembly/wasm-c-api /? WASM tutorial: https://www.google.com/search?q=wasm+tutorial /? WASM helloworld: https://www.google.com/search?q=wasm+helloworld Learn X in Y minutes > WebAssembly: https://learnxinyminutes.com/docs/wasm/ WebAssembly/WABT: The WebAssembly Binary Toolki

This seems sort of like understanding machine code vs assembly; it's much easier to learn WAT and translate to/from WASM as necessary using the wabt tools [0]. Either way its super cool how simple WebAssembly is, you can really get your hands dirty and understand exactly every detail of how your program runs! [0] https://github.com/WebAssembly/wabt

I think you're missing a good amount of nuance here minified JS can be turned into reasonable JS, yes, but you're probably not going to get TypeScript code back, so the same sort of challenge exists there. Assembly -> high-level language is harder, but there are absolutely binary -> C decompilers that are very popular/used in the RE community to make changes to existing programs. But that doesn't even matter, WASM is much higher level than assembly, it's a stack machine, there is no arbitrary control flow / labels / `goto`, there are pre-defined data types, etc. all of this means it's easier to convert WASM -> high-level language than it is with a generic x86/arm binary. There are WASM decompilers[0][1] which can convert WASM binaries into C code and back. In both cases (minified JS and WASM), you're not going to get out exactly what you

You mean this? https://github.com/WebAssembly/wabt/blob/main/wasm2c/README.... That seems like quite an undertaking. But at that point, It would make sense to cut out WASM entirely like https://datastation.multiprocess.io/blog/2022-05-12-sqlite-i...

> but i do not see you offering me a WASM runtime for the 8051 either As long as there’s a C compiler for it, just use https://github.com/WebAssembly/wabt/blob/main/wasm2c/README.... or https://github.com/turbolent/w2c2 That way, you get the portability of C, the optimisation power of GCC or your favourite C compiler and the portablity and determinism of WASM! Obviously there’s some overhead but there are definitely situations where this is a good option, especially where there’s a compiler available for WASM but not for whatever obscure platform you want to use