wasm-c-api

Wasm C API prototype

Web Development

Explore on GitHub Read Hacker News discussions

4Distinct people

4Mentions

0Explicit recommenders

612GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Wasm C API prototype

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year4 dated mentions

Observed mentions: 2020-03-15 14:57:47 UTC to 2025-02-03 15:16:00 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	1	1
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	1	1
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	0	0
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	1	1
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	0	0
2025	2025-01-01 00:00:00 UTC	2026-01-01 00:00:00 UTC	1	1

What Hacker News says

4 sources

syrusakbary·Feb 3, 2025

This is an interesting approach, great work! For anyone that wants to check where the meat is at, is mostly in this file: https://github.com/irrio/semblance/blob/main/src/wrun.c Thinking out loud, I think it would have been a great idea to conform with the Wasm-C-API (https://github.com/WebAssembly/wasm-c-api) as a standard interface for the project (which most of the Wasm runtimes: Wasmer, V8, wasmi, etc. have adopted), as the API is already in C and it would make it easier to try for developers familiar with that API. Note for the author: if you feel familiar enough with Wasm and you would like to contribute into Wasmer, we would also welcome any patches or improvements. Keep up the work work!

In I Wrote a WebAssembly VM in C

westurner·Dec 27, 2023

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

Read the rest

t: https://github.com/WebAssembly/wabt https://docs.docker.com/desktop/wasm/ : docker run \ --runtime=io.containerd.wasmedge.v1 \ --platform=wasi/wasm \ secondstate/rust-example-hello > Docker Desktop downloads and installs the following runtimes that you can use to run Wasm workloads: io.containerd.slight.v1 io.containerd.spin.v2 io.containerd.wasmedge.v1 io.containerd.wasmtime.v1 io.containerd.lunatic.v1 io.containerd.wws.v1 io.containerd.wasmer.v1 Do all of these have WASI?

In Ask HN: Best blog tutorial explaining Assembly code?

billconan·Jul 21, 2021

I'm not a native English speaker. The title got me confused. When looking at the title, I thought the article was about running a WASM module in a separate thread from a c/c++/rust program. For example: https://github.com/WebAssembly/wasm-c-api However, after reading it, it seems to be the opposite. It's about running a WASM module that has thread usage, implemented in c, c++ or rust. Then in that situation, I think the title should be rephrased as: Running WASM threads written in C, C++ or Rust. is it me or the use of "from" is misleading? is it "executed by/called from" or "compiled from" ? Sorry for asking this unrelated question. As a non-native speaker, every time I have this type of situation, I start to self-doubt.

In Using WebAssembly threads from C, C++ and Rust

follower·Mar 15, 2020

I've recently been working on WASM VM embedding with C (well, via libffi) for a personal project and uncovered a couple of WASM VM options, wasmtime & wasmer: * https://github.com/bytecodealliance/wasmtime * https://wasmerio.github.io/wasmer/c/runtime-c-api/ The underlying implementation of each is written in Rust. (Recently I also discovered there's a "micro VM" too: https://github.com/bytecodealliance/wasm-micro-runtime) The official WASM C API is still WIP but wasmtime targets it directly: https://github.com/WebAssembly/wasm-c-api/ Not sure if Wasmer is aiming for compatibility with the official WASM C API currently. From my experience, Wasmtime's C support is probably best described as "under-documented but functioning". I haven't implemented anything with Wasmer. My impression is that Wasmer may offer a higher level API than Wasmtime

Read the rest

but not sure if it counts as "drop in" yet. Part of the reason why I ended up going with Wasmtime was...I kinda forgot Wasmer existed. :D But also I do like that they're targeting what will hopefully become a standard API--but I think that results in a lower level API than what is most "friendly" for starting out. Been meaning to make this embedded Wasmtime C API example--created while figuring things out--public after tidying it up a bit more but... well, I just now made it public, as is (it at least has a ReadMe now :D ): https://gitlab.com/RancidBacon/wasm-embed-test :) Also, this is one option for test compiling C to WASM without setting up a tool chain: https://wasdk.github.io/WasmFiddle/ Some of my notes from development so far: http://www.labradoc.com/i/follower/p/notes-webassembly#20200... Edit: Grammar. Add & then move micro WASM VM link.

In WebAssembly brings extensibility to network proxies