HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
WebAssembly
proposals
Python2018–2025
WebAssembly / proposals

proposals

Tracking WebAssembly proposals

Web Development
Explore on GitHubRead Hacker News discussions
39Distinct people
49Mentions
0Explicit recommenders
1.1KGitHub stars
REPOSITORY AT A GLANCE

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

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.

0369122018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 11 mentions; 1 submissions, 10 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025

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.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC413
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC505
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC808
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC606
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC909
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC11110
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC404
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202

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 GitHub

What Hacker News says

9 sources
TUSF·Dec 2, 2022
> I don't think WASM should/would unify the GC across memory models WASM already has a GC proposal[0] which is already at the "Implementation stage"[1] so it looks like this IS going to happen, although it's uncertain if language runtimes like Go will actually make use of the feature, or what. [0]: https://github.com/WebAssembly/gc/blob/main/proposals/gc/Ove... [1]: https://github.com/WebAssembly/proposals A glance of the overview and spec seems to indicate that WASM will provide some primitive data types, and any GC language can build their implementation on top of it. As I understand it, it's heavily based on Reference Types[3], which allows acting on host-provided types, and is already considered part of the spec [4]. It doesn't remove the need for the 5 different runtimes to have their own GC, but it lowers the bulk that the runtimes
Read the rest
need to carry around, and offloads some of that onto the WASM runtime instead. [3]: https://github.com/WebAssembly/reference-types/blob/master/p... [4]: https://github.com/WebAssembly/proposals/blob/main/finished-...
In Extism: Make all software programmable with WebAssembly
adrianfcole·May 17, 2022
There's a proposals repo [1] that tracks the status of features like GC. According to that, GC is phase 2, which is prototyping [2]. To get to the finish line, implementations including at least 2 browsers need to happen (this is a Web standard, so there's some browser bias in the process). It is not straight forward to see who and what are implementing a proposal, especially if not tracked in the roadmap [3]. Best advice I could give for now is to watch the proposal repo [4], or just wait. It may be a while on this one. [1]: https://github.com/WebAssembly/proposals [2]: https://github.com/WebAssembly/meetings/blob/main/process/ph... [3]: https://webassembly.org/roadmap/ [4]: https://github.com/WebAssembly/gc
In Wazero: The zero dependency WebAssembly runtime for Go developers
tlively·Apr 20, 2022
The simplest way to get involved is to start attending the biweekly standardization meetings. The agendas are organized here: https://github.com/WebAssembly/meetings To attend the meetings, first join the W3C WebAssembly Community Group here: https://www.w3.org/groups/cg/webassembly, then email the CG chairs at webassembly-cg-chair@chromium.org to ask for an invite. From there you'll get a sense of who folks are so you can pair names with faces when contributing to the various proposal discussions on the many proposal repos listed here: https://github.com/webassembly/proposals. To get a sense of how things are run and decided, read the process documents here: https://github.com/WebAssembly/meetings/tree/main/process. The TL;DR is that the community group and its subgroups decide everything by consensus via votes during the meetings.
In WebAssembly 2.0 First Working Draft
richdougherty·Apr 19, 2022
It looks like garbage collection is at the 'proposal' stage, one step before it would start to be implemented. "During this phase: "One or more implementations proceed on prototyping the feature to the point that a comprehensive set of tests can be added. "A test suite is added. These tests need not pass the reference interpreter at this point, but should pass on some implementation." https://github.com/WebAssembly/proposals https://github.com/WebAssembly/meetings/blob/main/process/ph... Here's the proposal: https://github.com/WebAssembly/gc And you can see it's being actively worked on: https://github.com/WebAssembly/gc/commits/main
In WebAssembly 2.0 First Working Draft
chrismorgan·Feb 1, 2022
> WebAssembly will never have direct access to the DOM I haven’t been paying much attention to WASM proposals for the last few years, but I thought that direct DOM access (avoiding JavaScript trampolining) was one of the driving goals of the reference type, interface type and garbage collection proposals. https://github.com/WebAssembly/proposals/issues/16 mentions “call Web APIs (passing primitives or DOM/GC/Web API objects) directly from WebAssembly without calling through JavaScript”, and WASM’s high level goals document <https://github.com/WebAssembly/design/blob/main/HighLevelGoa...> lists “access browser functionality through the same Web APIs that are accessible to JavaScript” (not “through JavaScript”, but “through the same APIs”). Am I misunderstanding things?
In Pay attention to WebAssembly

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.