This is slightly wrong: Object rest and spread is not part of ES2015, it's actually a stage 2 proposal. [0]
Here's the list [1] of current proposals.
[0] https://github.com/sebmarkbage/ecmascript-rest-spread
[1] https://github.com/tc39/ecma262#current-proposals
In ES6 Rest/Spread, Defaults and Destructuringtc39
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, 6:01:32 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
5 sourcesES2016 Draft 1 and It Moves to GitHub
2 points · Open discussionInteresting, can you give a link? I tried to find it, it's not here https://github.com/tc39/ecma262 Only mention is "Typed objects" but that is not TS-like annotation.
In Node v4.0.0They list Intel's contribution extensively in the post. I'm not sure why you'd assume they are trying to deceive anyone.
> Intel has been contributing to Chakra, the JavaScript engine for Microsoft Edge
> Some examples of Intel’s direct contributions to Chakra’s JIT compiler include better instruction selection and scheduling.
> [they] also helped us identify opportunities of missed redundant instruction elimination, and inline overhead reduction.
> Intel engineers are collaborating with us closely to implement Single Instruction Multiple Data (SIMD) [1], a future ECMAScript proposal, in Chakra
> Intel recently contributed an optimization to improve navigation (load) time for pages containing several inline elements, optimizations to reduce DOM parse times for text-area elements, and participated in investigations and root cause analysis
Read the rest
to improve page load/response times
[1]: https://github.com/johnmccutchan/ecmascript_simd
[2]: https://github.com/tc39/ecma262