- rusty-wacc-viewer VS hn-search
- rusty-wacc-viewer VS wasmer
- rusty-wacc-viewer VS Graal
- rusty-wacc-viewer VS awesome-wasm-runtimes
- rusty-wacc-viewer VS cap-std
- rusty-wacc-viewer VS godot-wasm-engine
- rusty-wacc-viewer VS bsnes-plus-wasm
- rusty-wacc-viewer VS Uno Platform
- rusty-wacc-viewer VS watt
- rusty-wacc-viewer VS wasmtime
Rusty-wacc-viewer Alternatives
Similar projects and alternatives to rusty-wacc-viewer
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Graal
GraalVM compiles Java applications into native executables that start instantly, scale fast, and use fewer compute resources 🚀
-
Uno Platform
Build Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
rusty-wacc-viewer reviews and mentions
-
Why WebAssembly is innovative even outside the browser
While a "host" application (for the WASM runtime used) is required to enable access to graphical output (or user input) it doesn't have to be a browser.
At the (almost) most basic level a chunk of memory can be used as a framebuffer--the host application would read the pixel data which the WASM bytecode wrote and then write it to the host display via OS-level routines.
There are some plans/experiments at making a framebuffer "device" available as part of WASI.
I've written a couple of graphical WASM host applications that aren't browsers (and which don't use memory for pixel data transfer just integer values returned from a function):
The "WebAssembly Calling Card (WACC) Viewer" is implemented via the Godot game engine and an addon that integrates the Wasmtime WASM runtime with the engine: https://wacc.rancidbacon.com
(Also implemented a WACC Viewer in Rust: https://gitlab.com/RancidBacon/rusty-wacc-viewer)
WACC specifies how to transform three integer values (returned from a function in a WASM module) into a coloured triangle in order to render it on screen.
Another "host application" I implemented was a libretro compatible plugin that loads a WASM module and then feeds the module with input from libretro & retrieves framebuffer pixel data (one pixel at a time :D ) via a WASM function call & writes it to the libretro framebuffer for display.
Stats
Popular Comparisons
Sponsored