wasm-c-api
threads
| wasm-c-api | threads | |
|---|---|---|
| 2 | 16 | |
| 525 | 672 | |
| 1.1% | 1.3% | |
| 5.5 | 2.0 | |
| 12 months ago | 5 months ago | |
| C++ | WebAssembly | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
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.
wasm-c-api
-
Ask HN: Best blog tutorial explaining Assembly code?
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:
-
Using WebAssembly threads from C, C++ and Rust
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 from a c 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" ?
threads
-
No installation required: how WebAssembly is changing scientific computing
Similarly for threads: https://github.com/webassembly/threads
-
WebAssembly: Adding atomics waits to the main thread is the right thing to do
Specifically I submitted this to draw attention to the latest comment in the thread: https://github.com/WebAssembly/threads/issues/177
It's a good deep dive into how a small, but well-intentioned, browser choice nearly a decade ago led to poor outcomes for the WebAssembly ecosystem.
-
WASI Support in Go
The answer is: it's complicated. Which is most of the time the answer in the WASI world.
For this case it's complicated because some runtime supports https://github.com/WebAssembly/threads which mostly contains things like the spec for atomic but not the actual "threads" specs and then some runtimes (i.e wasmtime) also supports https://github.com/WebAssembly/wasi-threads which is one version of the threads. But a new proposal came into play https://github.com/abrown/thread-spawn so ... it's complicated.
-
WASM is the future?
There’s a proposal for threads
- Bringing Git in the browser via Go and WebAssembly. Upload, create files, folders, branches, commits etc... On the fly in the browser
-
LibreOffice running natively in a browser via WebAssembly
WebAssembly is having/going to have threads
https://github.com/WebAssembly/threads
-
The State of WebAssembly â 2021 and 2022
It's disappointing to see the WebAssembly/threads proposal is still only in proposal state, despite existing since 2018. It being just a proposal stops languages like golang from actually implementing support for it, despite Chrome supporting it since v70.
-
Using WebAssembly threads from C, C++ and Rust
Ah, I should have clarified that I mean the assembly instructions for atomics, rather than the JavaScript API. I.e. the opcodes listed here: https://github.com/WebAssembly/threads/blob/master/proposals...
-
AMA: We are Akhi, Alexandra, Islam, and Dimitris from the DFINITY Execution team. Ask us anything about building the execution layer.
Another point to add here is that the current wasm specification does not support threads although there is a proposal to add one. So I imagine that till the wasm specification includes it, we will continue to have only single threaded canisters.
What are some alternatives?
WASI - WebAssembly System Interface
webcontainer-core - Dev environments. In your web app.
onload - OpenOnload high performance user-level network stack
Uno Platform - Build Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported.
function-references - Proposal for Typed Function References
gc - Branch of the spec repo scoped to discussion of GC integration in WebAssembly
jupyterlite - Wasm powered Jupyter running in the browser 💡
biwascheme - Scheme interpreter written in JavaScript
schism - A self-hosting Scheme to WebAssembly compiler
motoko-token - The Token Package
ic - Internet Computer blockchain source: the client/replica software run by nodes
exception-handling - Proposal to add exception handling to WebAssembly