hn-search VS rusty-wacc-viewer

Compare hn-search vs rusty-wacc-viewer and see what are their differences.

Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
hn-search rusty-wacc-viewer
1,606 1
523 -
1.3% -
2.9 -
6 months ago -
TypeScript
GNU General Public License v3.0 or later -
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

hn-search

Posts with mentions or reviews of hn-search. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-16.

rusty-wacc-viewer

Posts with mentions or reviews of rusty-wacc-viewer. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-08-08.
  • Why WebAssembly is innovative even outside the browser
    11 projects | news.ycombinator.com | 8 Aug 2021
    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.

What are some alternatives?

When comparing hn-search and rusty-wacc-viewer you can also consider the following projects:

duckduckgo-locales - Translation files for <a href="https://duckduckgo.com"> </a>

wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten

v - Simple, fast, safe, compiled language for developing maintainable software. Compiles itself in <1s with zero library dependencies. Supports automatic C => V translation. https://vlang.io

Graal - GraalVM compiles Java applications into native executables that start instantly, scale fast, and use fewer compute resources 🚀

parser - 📜 Extract meaningful content from the chaos of a web page

awesome-wasm-runtimes - A list of webassemby runtimes

readability - A standalone version of the readability lib

cap-std - Capability-oriented version of the Rust standard library

yq - Command-line YAML, XML, TOML processor - jq wrapper for YAML/XML/TOML documents

godot-wasm-engine

milkdown - 🍼 Plugin driven WYSIWYG markdown editor framework.

bsnes-plus-wasm - debug-oriented fork of bsnes, with added wasm runtime for scripting