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, 4:01:40 AM 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

4 sources
kristiandupont·Dec 16, 2018
>there will never be direct DOM access from WebAssembly for security reasons You should contribute this knowledge: https://github.com/WebAssembly/proposals/issues/16 >developers, [...], tend to be deathly afraid of touching the DOM I truly have never seen this. In fact, I'd say I often see a rather careless culture of doing DOM manipulation here and there because it solves an immediate problem, albeit by short-circuiting the abstractions that may be in place and are now a bit more fragile. I am writing JS in the entire stack at the moment and I am mostly happy with it. I don't think that ability will go away but I look forward to the day where I can do the same in Rust or F# or whatever. And it doesn't seem unlikely to me that one day we will see wasm becoming the foundation in browsers, with JS running on top of it like any other languag
Read the rest
e.
In Rust and WebAssembly in 2019
kodablah·Oct 30, 2018
Quick notes... The threads feature is in proposed status vs others that are in implementation status [0], but I assume this has been implemented before things like multi-value. I wonder why threads first, I assume just for experimentation. It should be noted that threads are essentially atomic memory accesses and wait/notify, nothing for starting a worker inside of WASM or anything, that is still in JS land. The test cases don't appear to include wait/wake nor does the test case interpreter that I saw [1]. Also, "Report issues" in the blog post links to https://TBD. 0 - https://github.com/WebAssembly/proposals 1 - https://github.com/WebAssembly/threads
In WebAssembly Threads ready to try in Chrome 70
kodablah·Oct 22, 2018
Here's a newly created proposals repo to keep track: https://github.com/WebAssembly/proposals. > Skill: 64-bit addressing As a WASM backend implementer in an environment w/ only 32-bit addresses, I hope people don't move to 64-bit addresses too soon. Are we really reaching the limits here already? > Skill: Portability [...] A POSIX for WebAssembly if you will. A PWSIX? A portable WebAssembly system interface. Yes please, but dev'd outside of WebAssembly. This is needed for interoperability between languages. Even just strings would be nice. A stdlib interface to rule them all, so to speak. If kept modular and avoided a lot of bikeshedding and had a full test suite, it could have a great benefit even outside of WASM.
In WebAssembly’s post-MVP future

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.