This is the proposal tracking this: https://github.com/WebAssembly/proposals/issues/16
No recent updates unfortunately.
In WebAssembly StudioWebAssembly
proposals
Python2018–2025
WebAssembly / proposals
proposals
Tracking WebAssembly proposals
39Distinct people
49Mentions
0Explicit recommenders
1.1KGitHub stars
What to know before exploring
What it is
Tracking WebAssembly proposals
GitHub
Where it is used
No documented product use was verified in the last source check.
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
- webassembly/gc · linked in 4 of the same discussions
- webassembly/meetings · linked in 4 of the same discussions
- webassembly/interface-types · linked in 3 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:03:30 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 year49 dated mentions
Observed mentions: 2018-10-22 17:05:09 UTC to 2025-05-10 00:07:26 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
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 8 | 0 | 8 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 6 | 0 | 6 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 9 | 0 | 9 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 11 | 1 | 10 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 2 | 0 | 2 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
WebAssembly proposals
Finished Proposals
Inactive Proposals
Active proposals
Proposals follow this process document.
Phase 5 - The Feature is Standardized (WG)
These proposals have not yet been merged to the spec. Merged proposals are listed in Finished Proposals.
Proposal
Champion
JS Promise Integration
Francis McCabe
Web Content Security Policy
Francis McCabe
Phase 4 - Standardize the Feature (WG)
Proposal
Champion
Threads
Conrad Watt
Compact Import Section
Ryan Hunt
Wide Arithmetic
Alex Crichton and Jamey Sharp
Phase 3 - Implementation Phase (CG + WG)
Proposal
Champion
ESM Integration
Asumu Takikawa, Ms2ger, and Guy Bedford
Stack Switching
Francis McCabe and Sam Lindley
Custom Page Sizes
Nick Fitzgerald
Custom Descriptors and JS Interop
Thomas Lively
Phase 2 - Proposed Spec Text Available (CG + WG)
Proposal
Champion
Relaxed dead code validation
Conrad Watt and Ross Tate
Numeric Values in WAT Data Segments
Ezzat Chamudi
Extended Name Section
Ben Visness
Rounding Variants
Kloud Koder
Compilation Hints
Emanuel Ziegler
JS Primitive Builtins
Sébastien Doeraene
Acquire-Release Atomics
Conrad Watt and Rezvan Mahdavi Hezaveh
Multibyte Array Access
Brendan Dahl
FP16
Brendan Dahl
Phase 1 - Feature Proposal (CG)
Proposal
Champion
Type Imports
Andreas Rossberg
Component Model
Luke Wagner
WebAssembly C and C++ API
Andreas Rossberg
Flexible Vectors
Petr Penzin and Tal Garfinkel
Memory control
Deepti Gandluri and Ben Visness
Reference-Typed Strings
Andy Wingo
Profiles
Andreas Rossberg
Shared-Everything Threads
Andrew Brown, Conrad Watt, and Thomas Lively
Frozen Values
Léo Andrès and Pierre Chambart
More Array Constructors
Nick Fitzgerald
JIT Interface
Ben Titzer
Type Reflection for WebAssembly JavaScript API
Ilya Rezvov
JS Text Encoding Builtins
Daxpedda
Phase 0 - Pre-Proposal (CG)
Phase 0 proposals are tracked in the design repository issue tracker.
Implementation status
Implementation status of most proposals in various wasm engines is available on https://webassembly.org/features/
Contributing new proposals
Please see Contributing to WebAssembly for the most up-to-date information on contributing proposals to standard.
Read the full README on GitHubWhat Hacker News says
8 sourcesIt does feel like WebAssembly development has stalled after the initial release. There are proposals for reference types, garbage collection, and host bindings that would greatly expand a WebAssembly binary's capabilities, but they haven't been implemented in any browser, much less standardized yet.
WebAssembly proposals tracker: https://github.com/WebAssembly/proposals
WebAssembly reference types (https://github.com/WebAssembly/reference-types/blob/master/p...) looks like the blocker for a lot of things, and it's in the final spec phase at least.
In Chrome, it's behind a flag since 78, which went stable in Oct 22 2019: https://chromestatus.com/features/5166497248837632
But also under active development? https://bugs.chromium.org/p/v8/issues/detail?id=7581
Supposedly implemented in Firefox two years ago: https://bugzilla.mozilla.org/sho
Read the rest
w_bug.cgi?id=1444925
Nothing in Safari, of course.
Where is it now though?
Yet. Support for these and more is coming: https://github.com/webassembly/proposals
In WebAssembly without the browserI suspect it won't really hit until the changes that enable direct DOM access, and things that make dynamic languages easier to implement in WASM. These things: https://github.com/WebAssembly/proposals/issues/16
In Single Page Applications using RustIt seems like the WASM folks have a plan to address it in the future. https://github.com/WebAssembly/proposals/issues/16
In Golang Desktop App with Webview/Lorca, WASM and BazelV8, JVM, CLR and others are well proven runtimes providing a well functioning sandbox, but of course we test a lot. I am sure you know what the risks are with native code - you're a native code proponent after all; any code running in a medium and bigger company that could misplace money is a huge liability.
I don't know what magic you're talking about - we're simply waiting for WASM to standardize GC, SIMD, tail calls etc, you can read more here[0]; and to get the execution optimized like V8 did over the past 10 years[1] (WASM on V8 gets most of these gains by default as a bonus).
I already said why I want WASM: because it provides a good sandbox and opens most ecosystems through safe and typed interop. I don't care about ES modules in particular - I care about ES modules, Ruby modules, Python modules, Prolog modules, Fortran modules, C
Read the rest
modules, Rust modules, AssemblyScript modules, COBOL modules, Erlang modules, F# modules, Java modules, and so on - at once. Finally a future where I can use and trust any library and not get limited to the language I use (if I don't want to spend most of my time fighting and securing C ABI interop, if at all humanly possible) is there.
[0] https://github.com/WebAssembly/proposals
[1] https://v8.dev/blog/10-years#performance-ups-and-downs
Threads. There's going to be a lot of 'throw threads at it and hope performance issues go away'-type solutions.
https://github.com/WebAssembly/proposals/issues/14
In Ryzen Threadripper Pro 3995WX SpottedI think the future is still hazy for managed languages, the GC side of Wasm is still in the design phase and it's not clear how widely it will be implemented. And it's been quiet for a long time, is the effor even alive? (https://github.com/WebAssembly/proposals/issues/16)
If it's going to encompass the possibility to hook into the JS side GC engine, this might not be implemented at all in headless Wasm applications, and so you wouldn't be able to use the GC'd languages on those platforms, just C(++)/Rust. Which is not very attractive compared to the easier / safer high level languages most programmers are used to.
In WebAssembly brings extensibility to network proxies