wabt VS linguist

https://github.com/WebAssembly/wabt/blob/main/wasm2c/README.... is a straightforward way to take an untrusted application (compiled already to wasm) and turn it into C that you can embed into your application or compile to a linkable DLL. I believe this approach has been used to sandbox untrusted libraries in production by Mozilla: https://hacks.mozilla.org/2021/12/webassembly-and-back-again...

As long as this is happening, might as well try some of my favorites: https://github.com/wasm3/wasm3, https://github.com/WebAssembly/wabt, https://github.com/bytecodealliance/wasmtime

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

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...

The .wat file can be compiled to a .wasm using wat2wasm which is part of the WebAssembly Toolkit CLI tools:

it is in C++ https://github.com/WebAssembly/wabt/blob/main/src/tools/wat2wasm.cc

I don't think you are building an application that will use Native Client technologies How to extract source code from Native Client .nexe file, migrate to WebAssembly? #1864 so that would be superfluous, and frankly, useless in your case.

I'm trying to get a basic Rust webassembly program, then porting it to C via wasm2c. The example works, but when I use wasm-bindgen and analyze it with wasm2wat, I get an import "env". The issue is that in C (wasm2c) it comes out as struct Z_env_instance_t; and I can't instantiate it (as in Z_env_instance_t env; to pass it's address to Z_wasm_client_bg_instantiate.

I dunno if this interests you, but you actually have influence over the formatting of https://github.com/someengineering/fix-cf/blob/main/fix-role... via .gitattributes communicating to GH that it's actually yaml: https://github.com/github-linguist/linguist/blob/master/docs...

There’s already a draft pr for this: https://github.com/github-linguist/linguist/pull/6686

GitHub uses Linguist to

I have found that: https://github.com/github-linguist/linguist/blob/master/docs/troubleshooting.md, but I'm also currently not at home, so I will check it out later.

Another option is to use Linguist which is what GitHub uses (I use linguist via .gitattributes files for all of my code projects). It is community driven and supports essentially every language possible: see languages.yml.

Once you selected a topic you can further filter the projects by language. This means programming language as recognized by the linguist tool of GitHub. See what they say about repository languages

As I later found out, GitHub uses the Linguist library to measure the amount of lines written in a specific language... which is still pretty magic 🪄.