Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR. Learn more →
Top 10 WebAssembly Proposal Projects
-
Project mention: Kickstart insight needed: A new retrofitted C dialect? | news.ycombinator.com | 2025-02-22
Destructors? Destructors are fine as a feature. You're not supposed to use them as the first choice but they are a great "safety net" for disposable types that did not get dispose to ensure that production code stays resilient to unmanaged memory leaks when presented with bad code.
Either way, you can read through this issue: https://github.com/WebAssembly/gc/issues/77
Further discussion can be found here: https://github.com/dotnet/runtime/issues/94420
Turning off destructors will not help even a little because the biggest pain points are support for byref pointers and insufficient degree of control over object memory layout.
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
-
-
Interesting!
https://github.com/WebAssembly/multi-memory/blob/main/propos...
The scaling point is what I was thinking of.
"As long as Wasm memories are limited to 32 bit address space, there is no way to scale out of 4 GB memory efficiently. Multiple memories at least provide an efficient workaround until 64 bit memories become available (which may still take a while)."
-
WASM does appear to have significant tailcall consideration: https://github.com/WebAssembly/tail-call/blob/main/proposals...
-
-
Project mention: Why is WebAssembly not supporting 256/512 SIMD registers? | news.ycombinator.com | 2024-05-24
Registers will keep growing. Rather than adding 512 bits to the spec, it's better to choose an abstraction that's portable across hardware, so that modules don't need to be recompiled every few years with the latest and greatest SIMD size.
There's a proposal called 'flexible-vectors' which is still in stage 1 (i.e. design phase). Its goal is length-agnostic SIMD.
https://github.com/WebAssembly/flexible-vectors
-
Nutrient
Nutrient - The #1 PDF SDK Library. Bad PDFs = bad UX. Slow load times, broken annotations, clunky UX frustrates users. Nutrient’s PDF SDKs gives seamless document experiences, fast rendering, annotations, real-time collaboration, 100+ features. Used by 10K+ devs, serving ~half a billion users worldwide. Explore the SDK for free.
-
-
Apart from WebAssembly modules operating exclusively on scalar input arguments (e.g., computing the sine of a single number), every WebAssembly module instance must be associated with WebAssembly memory, which is allocated in fixed increments of 64KiB (i.e., a "page"). And importantly, as of this blog post, WebAssembly memory can only grow and never shrink. As there is currently no mechanism for releasing memory to a host, a WebAssembly application's memory footprint can only increase. These two aspects combined increase the likelihood of allocating memory which is never used and the prevalence of memory leaks.
-
NOTE:
The open source projects on this list are ordered by number of github stars.
The number of mentions indicates repo mentiontions in the last 12 Months or
since we started tracking (Dec 2020).
WebAssembly Proposal discussion
WebAssembly Proposal related posts
-
A Gentle Introduction to WebAssembly in Rust (2025 Edition)
-
Revisiting the DOS Memory Models
-
WASM memory64 reaches stage 4
-
Memory Control Proposal for WebAssembly
-
Why Google Sheets ported its calculation worker from JavaScript to WasmGC
-
Why is WebAssembly not supporting 256/512 SIMD registers?
-
Old CSS, new CSS (2020)
-
A note from our sponsor - CodeRabbit
coderabbit.ai | 15 Mar 2025
Index
What are some of the best open-source Proposal projects in WebAssembly? This list will help you:
| # | Project | Stars |
|---|---|---|
| 1 | gc | 1,032 |
| 2 | threads | 717 |
| 3 | exception-handling | 165 |
| 4 | multi-memory | 132 |
| 5 | tail-call | 113 |
| 6 | function-references | 101 |
| 7 | flexible-vectors | 50 |
| 8 | relaxed-simd | 43 |
| 9 | memory-control | 42 |
| 10 | proposal-type-imports | 22 |
Sponsored
CodeRabbit: AI Code Reviews for Developers
Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
coderabbit.ai