wgpu-native VS wasmdec

The Mach engine project has prebuilt Dawn libraries and also a simplified build-from-source process using the Zig build system, see:

https://machengine.org/pkg/mach-gpu-dawn/

It's also possible to use wgpu-native in C/C++ projects as prebuilt library, see:

https://github.com/gfx-rs/wgpu-native

It is based on the wgpu-native implementation (Firefox backend) but I plan on adding a receipe for using it with Dawn (Chrome backend) as well.

go-webgpu provides binding for wgpu-native (a safe and portable GPU abstraction in Rust, implementing WebGPU API).

Rust, C++

When you look at graphics APIs in Rust practically everything is pointing towards, and telling you to use, wgpu, which abstracts over Vulkan, Metal, DX11/12, GLES and WebGPU and is based on, drumroll, WebGPU. Hardly surprising as it's the backend firefox is going to use. And yes it has a C API, too.

Probably the easiest option would be to target wgpu-native prebuilt binaries but these don't have iOS/Android (unsure if wgpu-native supports iOS/Android at all)

WGPU is the underlying implementation for WebGPU in Firefox and it has C bindings: https://github.com/gfx-rs/wgpu-native.git.

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 put in, but WASM doesn't really change the situation very much given the widespread adoption of 'compile to JS' languages like TypeScript these days.

[0] https://chromium.googlesource.com/external/github.com/WebAss...

[1] https://github.com/wwwg/wasmdec

There are wasm2c and wasmdec that decompile to C. There is also rewasm, which decompiles WASM to Rust. But I don't know if they can reconstruct non-trivial logic, e.g. shapes of structures.

Have you considered just transpiling it to C? Assuming it's the pseudocode you're after, that should be enough by itself. You could also lift it and recompile to whatever your preferred architecture is.

This is not less portable and will beat any wasm interpreter in terms of speed: https://github.com/wwwg/wasmdec