I haven't done it, but if you want to propose a change to JavaScript, it looks like there is a process to follow, and it doesn't necessarily involve spending money:
https://github.com/tc39/ecma262/blob/master/CONTRIBUTING.md
In De-facto closed source: the case for understandable softwaretc39
ecma262
HTML2015–2026
tc39 / ecma262
ecma262
Status, process, and documents for ECMA-262
44Distinct people
46Mentions
1Explicit recommenders
15.7KGitHub stars
What to know before exploring
What it is
Status, process, and documents for ECMA-262
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
It would be interesting if browsers supported more languages but I don't mind the monoculture. I have spent a lot of time investing in languages, frameworks and tools, so much…
benoau used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- tc39/proposal-ptc-syntax · linked in 4 of the same discussions
- tc39/proposal-object-rest-spread · linked in 2 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, 7:24:48 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 year46 dated mentions
Observed mentions: 2015-05-22 08:40:24 UTC to 2026-10-29 16:46:08 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
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 |
|---|---|---|---|---|---|
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 5 | 1 | 4 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 9 | 1 | 8 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 7 | 3 | 4 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 7 | 3 | 4 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 2 | 2 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
ECMAScript
This repo
This repository contains the source for the current draft of ECMA-262,
the ECMAScript® Language Specification.
This source is processed to obtain a human-readable version,
which you can view here.
If you want to explore how the specification was written, you can also view the source with its history in searchfox.
Current Proposals
Proposals follow the TC39 process and are tracked in the proposals repository.
Finished Proposals
Active Proposals
Stage 1 Proposals
Stage 0 Proposals
Inactive Proposals
Contributing New Proposals
Please see Contributing to ECMAScript for the most up-to-date information on contributing proposals to this standard.
Developing the Specification
After cloning, do npm install to set up your environment. You can then do npm run build to build the spec or npm run watch to set up a continuous build. The results will appear in the out directory, which you can use npm run clean to delete.
Community
ES discourse: Forum for ECMAScript discussion and questions
Matrix: Chat
Read the full README on GitHubWhat Hacker News says
7 sourcesI found [this pull request] that adds language recommending the use of semicolons, but no proposals to require semicolons or to remove Automatic Semicolon Insertion.
Removing ASI from ECMAScript would break backwards compatibility - modern JS engines couldn't run scripts that use ASI which would break a lot of websites that are alread deployed. ECMA will add features that won't run in old engines (older V8 can't parse arrow functions) but they won't add/remove/change features that break existing behavior.
Today there are code patterns where ASI is ambiguous, or at-least hard for a developer to grok. TC39 is warning developers that new language features will not be designed for ASI and might have confusing behavior if those new features are used without semicolons.
[this pull request]: https://github.com/tc39/ecma262/pull/1062/files
In Propel – Machine learning for JavascriptCan you provide a source for that?
Closest thing I could find was this, which simply adds an ASI hazard clause: https://github.com/tc39/ecma262/pull/1062
In Propel – Machine learning for Javascriptv8 did and then pulled support. JSC (javascript core) added support in June/July 2016 (a year and a half ago). Their team makes some great points about this.
https://github.com/tc39/ecma262/issues/535
https://github.com/rwaldron/tc39-notes/blob/master/es7/2016-...
For all of Google's talk about their syntactic tail call proposal, they haven't cared enough to implement it -- only to remove their PTC code. FF and MS are in the same position. At this point, I don't really care one way or the other, they need to quit the excuses, quit the petty power struggles, and do something one way or the other. Every year they wait is another year before we can use it.
EDIT: I'd also add that the performance impact in the real world seems to be close to zero.
https://github.com/tc39/proposal-ptc-syntax/issues/7
In V8 JavaScript Engine Release v6.5ECMAScript is documenting for developers to avoid ASI
1 points · Open discussionAsync Iterators received Stage 4 and will be in ECMAScript 2018
1 points · Open discussionECMA262: Add Automatic Semicolon Insertion hazard clause
4 points · Open discussion