tc39/ecma262 on Hacker News

…in a good place - open standard, open governance, open to proposals, massive open source culture. https://github.com/tc39/ecma262/blob/main/CONTRIBUTING.md#ne...

comment by benoau · 2026-10-29 · in The Web Can't Afford a JavaScript Runtime Monoculture

…start? In terms of standard, the specs already use "ECMAScript" and don't even mention JavaScript ( https://github.com/tc39/ecma262/ ), although TC39 website does use it frequently. I guess they could officially recommend people stop using…

comment by rs186 · 2025-12-04 · in It’s time to free JavaScript (2024)

…resources (bad, but sometimes tolerable) or worse, use-after-free bugs (outright fatal) – see e.g. https://github.com/tc39/ecma262/issues/2650

comment by pwdisswordfishz · 2025-05-17 · in JavaScript's New Superpower: Explicit Resource Management

▲ 3

ECMAScript 2024

story by uallo · 2024-06-27 · 1 comment

▲ 80

TC39: Add Object.groupBy and Map.groupBy

story by moritzwarhier · 2023-12-19 · 61 comments

▲ 1

Document.all Willful Violation

story by aragonite · 2023-10-15 · 0 comments

…opposed to versions of it that would remove/unrequire the tail-call optimisation they already do: https://github.com/tc39/ecma262/issues/535 For the version of it that is backwards compatible, they wouldn’t need to do anything other than…

comment by systoll · 2022-07-13 · in Tell HN: We are trying to get tail calls into the WebAssembly standard

…Apple's 2016 response as to why they won't implement STC is here: https://github.com/tc39/ecma262/issues/535 - STC is part of the spec and will take too long to change. - Now that they've implemented support for PTC, they do

comment by richdougherty · 2022-06-15 · in What happened to proper tail calls in JavaScript? (2021)

…that when an object becomes eligible for finalization in the first place is… not at all obvious: < https://github.com/tc39/ecma262/issues/2650 >.

comment by pwdisswordfish9 · 2022-04-23 · in JavaScript Garbage Collection with WebAssembly Is Possible Today

…Nope. It is relevant. For the stuff you put between script tags there's at the very least https://github.com/tc39/ecma262 that you can look at and tell exactly what's going on with your code. With Vue (and, yes, React and Svelte and…

comment by dmitriid · 2021-08-03 · in Vue.js is Wikimedia Foundation's future JavaScript framework

…a language feature before, but after 2 minutes of googling, this actually looks completely doable: https://github.com/tc39/ecma262/blob/master/CONTRIBUTING.md So, impostor syndrome aside, why not? Wanna team up on that?

comment by golergka · 2021-04-13 · in Using the switch(true) pattern in JavaScript

…5: https://github.com/tc39/notes/blob/master/meetings/2018-01/j... 6: https://github.com/tc39/ecma262/issues

comment by IainIreland · 2020-06-13 · in A New RegExp Engine in SpiderMonkey

…rejected it. Rather than fixing the browsers, the spec was changed in ES8 to reflect "web-reality". https://github.com/tc39/ecma262/pull/303 Browsers could have become ES6 compliant here, with zero compatibility risk. But when there is…

comment by ridiculous_fish · 2020-06-12 · in A New RegExp Engine in SpiderMonkey

Cool. I wasn't aware Chrome re-enabled SABs, with mitigations. https://github.com/tc39/ecma262/issues/1435

comment by animalCrax0rz · 2020-04-10 · in Make Linux Fast Again (2019)

…proposal was actually made because all major browsers had switched to a stable sort implementation: https://github.com/tc39/ecma262/pull/1340 It was actually proposed by the v8 / chrome people ( https://v8.dev/features/stable-sort ) after…

comment by masklinn · 2019-12-07 · in New Features in ES2019

This one: https://github.com/tc39/ecma262

comment by inimino · 2019-09-25 · in Prashanth Chandrasekar Replacing Joel Spolsky as Stack Overflow CEO

▲ 2

Update in ES spec makes async functions way faster

story by ecares · 2019-02-28 · 1 comment

…interested, here's a ticket from TC39 proposing directly discussing possible issues with ASI: https://github.com/tc39/ecma262/pull/1062/files Point being they're not advocating for using semicolons, but making it clear what the possible…

comment by ng12 · 2019-02-12 · in Can You Find the Bug in This Code?

…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

comment by skybrian · 2018-12-01 · in De-facto closed source: the case for understandable software

…have confusing behavior if those new features are used without semicolons. [this pull request]: https://github.com/tc39/ecma262/pull/1062/files

comment by seniorsassycat · 2018-02-26 · in Propel – Machine learning for Javascript

…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

comment by kevincennis · 2018-02-26 · in Propel – Machine learning for Javascript

…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…

comment by hajile · 2018-02-02 · in V8 JavaScript Engine Release v6.5

▲ 1

ECMAScript is documenting for developers to avoid ASI

story by fagnerbrack · 2018-02-01 · 0 comments

▲ 1

Async Iterators received Stage 4 and will be in ECMAScript 2018

story by zbraniecki · 2018-01-25 · 0 comments

▲ 4

ECMA262: Add Automatic Semicolon Insertion hazard clause

story by mulltiq · 2018-01-12 · 0 comments

▲ 2

TC39 Pull Request for Object Rest/Spread

story by styfle · 2017-12-19 · 0 comments

▲ 1

How to Contribute to ECMAScript spec

story by fagnerbrack · 2017-12-11 · 0 comments

…into a proposal and shepherd it into the language. Apparently here: https://esdiscuss.org/ [1] https://github.com/tc39/ecma262/blob/master/CONTRIBUTING.md

comment by pier25 · 2017-11-14 · in Types in JavaScript: why you should care

…not too much gain. Willing to go back on this. You can always watch the commits go in here though: https://github.com/tc39/ecma262/commits/master .

comment by bterlson · 2017-11-07 · in ECMAScript 2018 Language Specification

…2017. Looking at the Github repo, you can see that they changed it from 2017 to 2018 on March 31st: https://github.com/tc39/ecma262/commit/8340bf9a8427ea81bb0d1... So what happened to 2017?

comment by pc2g4d · 2017-11-07 · in ECMAScript 2018 Language Specification

▲ 2

JavaScript: Are keywords (ab)used too much in upcoming proposals?

story by dmitriid · 2017-08-06 · 0 comments

They forgot to include JavaScript which is at https://github.com/tc39/ecma262

comment by SimeVidas · 2017-01-03 · in Programming languages that are actively developed on GitHub

…were against "TCO" as an optional optimization, however they are the first to implement PTC. [0] https://github.com/tc39/ecma262/issues/535

comment by Klathmon · 2016-12-19 · in Cancelable Promises: Why was this proposal withdrawn?

▲ 2

Document.all willful violation

story by yuhong · 2016-08-19 · 1 comment

…, this syntax is still seen on the web, and any such pages would be broken by this change. https://github.com/tc39/ecma262/issues/260

comment by uwu · 2016-07-06 · in Safari Tech Preview 8 achieves 100% ES6 support

…view. We've been discussing pros and cons at https://github.com/tc39/proposal-ptc-syntax/issues and https://github.com/tc39/ecma262/issues/535 , and it'd be great to have your input, including the overturning-prior-consensus issues you…

comment by LittleDan · 2016-04-29 · in ES6, ES7, and beyond

…are actually part of ES2015. They're both TC39 proposals, at various stages of completion: https://github.com/tc39/ecma262 . Very justifiably, neither Babel 5 nor Babel 6 transpiled those out-of-the-box by default; for novice programmers,…

comment by taion · 2016-03-28 · in Babel 6 – useless by default

…like they will be anytime soon. I guess they have some staging system and it's still at stage 0 ( https://github.com/tc39/ecma262/blob/master/stage0.md ), grouped with lookbehind assertions, named captures, and mode modifiers.

comment by deadowl · 2016-03-24 · in NPM and Left-Pad: Have We Forgotten How to Program?

…need to happen before node can even consider this… 1. TC39 needs to get async functions to stage 4: https://github.com/tc39/ecma262/blob/master/README.md 2. V8 needs to implement: https://github.com/nodejs/promises/issues/4 3. Node then…

comment by secoif · 2016-02-26 · in Node 5.7.0 (stable) released

…standard yet. It's a stage 3 proposal at this time, which means it may not even land in ES 2016: https://github.com/tc39/ecma262 The last thing we want is native support for pre-standard features. As long as it's not in a spec (or draft at…

comment by pluma · 2016-02-26 · in Node 5.7.0 (stable) released

…theories. The environment is significantly different than it was during the early IE days. https://github.com/tc39/ecma262

comment by rapind · 2016-01-11 · in YouTube change served lower-quality video to Firefox 43 for 2 weeks

…the list [1] of current proposals. [0] https://github.com/sebmarkbage/ecmascript-rest-spread [1] https://github.com/tc39/ecma262#current-proposals

comment by TheAceOfHearts · 2015-12-28 · in ES6 Rest/Spread, Defaults and Destructuring

Stage 2 https://github.com/tc39/ecma262 https://github.com/sebmarkbage/ecmascript-rest-spread

comment by Keithamus · 2015-10-30 · in Node.js 5.0 Released

▲ 2

ES2016 Draft 1 and It Moves to GitHub

story by obilgic · 2015-09-23 · 0 comments

Interesting, 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.

comment by Ciantic · 2015-09-09 · in Node v4.0.0

…to improve page load/response times [1]: https://github.com/johnmccutchan/ecmascript_simd [2]: https://github.com/tc39/ecma262

comment by mkishi · 2015-05-22 · in Intel’s contributions in Microsoft Edge: SIMD and other performance enhancements