TC39

TC39
Name	TC39
Type	Standards committee
Formed	1996
Headquarters	Redmond, Washington
Parent organization	Ecma International
Fields	ECMAScript, JavaScript
Website	Official

TC39 is the technical committee of Ecma International responsible for the evolution of the ECMAScript language, commonly implemented as JavaScript. The committee convenes representatives from major technology companies, standards organizations, and browser vendors to propose, refine, and ratify language features used across Node.js, V8, SpiderMonkey, and JavaScriptCore. Its work impacts projects such as React, Angular, Vue.js, and runtimes like Deno.

History

TC39 was established within Ecma International amid discussions following the release of the ECMA-262 specification and the proliferation of Netscape Navigator and Microsoft Internet Explorer during the 1990s. Early milestones include coordination with companies like Netscape Communications Corporation, Microsoft Corporation, Sun Microsystems, and IBM to stabilize ECMAScript 1st edition. Subsequent editions involved stakeholders such as Google LLC, Mozilla Foundation, Apple Inc., and Intel Corporation in responding to influences from projects such as Ajax and the Dojo Toolkit. The committee’s modernization efforts paralleled events including the rise of ECMAScript 3rd edition and the later harmonization leading to ECMAScript 5th edition and the significant overhaul that produced ECMAScript 6th edition (also known as ECMAScript 2015). Notable external influences included the evolution of CommonJS proposals, debates exemplified by participants from Yahoo!, Facebook, Inc. and contributors to jQuery, and the broader open-source ecosystem represented by GitHub and npm, Inc..

Organization and Membership

Membership comprises appointed delegates from corporations, browser vendors, and standards bodies such as Microsoft Corporation, Google LLC, Mozilla Foundation, Apple Inc., Intel Corporation, Facebook, Inc. (Meta Platforms, Inc.), Samsung Electronics, Alibaba Group, Tencent, IBM, Oracle Corporation, Adobe Inc., Netflix, Inc., Airbnb, Inc. and independent experts affiliated with institutions like MIT, Stanford University, University of California, Berkeley, ETH Zurich and University of Cambridge. Liaison organizations include W3C, ISO, and IETF. Working groups and editors have included prominent implementers from V8, SpiderMonkey, JavaScriptCore, and maintainers associated with projects such as Babel, TypeScript, Flow, and Webpack. Leadership roles like chair, editors, and secretary have been held by representatives allied with Ecma International and participant organizations.

Standards Process and Proposal Stages

The standards workflow uses a multi-stage process for proposals labeled Stage 0 through Stage 4 in coordination with Ecma International procedures and influenced by precedents from IETF and W3C processes. Proposals originate as GitHub repositories, ECMA-262 supplements, or drafts from companies such as Google LLC (e.g., V8 proposals), Microsoft Corporation (e.g., TypeScript-adjacent ideas), or academic inputs from MIT and Stanford University. Stage 0 captures ideas from participants like authors of Async/await proposals and transpilers such as Babel. Stage 1 requirements and semantics discussions often reference implementations in Node.js and engines like ChakraCore. Stage 2 formalizes syntax and semantics with test262 conformance tests produced collaboratively by entities including Mozilla Foundation and Google LLC. Stage 3 seeks consensus and implementation experience from WebKit and Chromium embedders. Stage 4 ratifies features into ECMA-262 editions, after which features are implemented by projects like V8, SpiderMonkey, JavaScriptCore and adopted by frameworks such as React and Angular.

Notable ECMAScript Features and Editions

Editions reflect coordinated releases such as ECMAScript 5th edition and ECMAScript 2015 (6th edition), with major features including arrow function-style proposals, class syntax, Promises, ECMAScript Modules, let and const bindings, and generators. Later editions introduced async/await, Symbols, Proxys, and Reflect APIs. Stage-driven additions have included Optional chaining, Nullish coalescing operator, BigInt, Intl updates, Temporal, and Records and Tuples. Runtime- and engine-level impacts are seen in V8 performance patches, SpiderMonkey optimizations, and JavaScriptCore JIT improvements affecting deployments on platforms like Android and iOS. The committee’s output interacts with ecosystem tooling such as Babel, TypeScript, ESLint, Prettier, and package ecosystems like npm, Inc..

Meetings and Governance

Meetings follow agendas set by chairs and editors under Ecma International governance, often held in cities such as Redmond, Washington, San Francisco, London, Berlin, Tokyo, and Beijing. Minutes, agenda items, and proposal reviews are coordinated through channels including GitHub, mailing lists tied to Ecma International, and presentations at conferences like JSConf, NodeConf, Google I/O, WWDC, Microsoft Build, and Mozilla Festival. Governance includes voting procedures among member delegations representing organizations such as Microsoft Corporation, Google LLC, Apple Inc., Mozilla Foundation, and IBM with oversight from Ecma International secretariat staff and liaisons to bodies like ISO/IEC.

Criticism and Controversies

The committee has faced controversy over feature prioritization, compatibility trade-offs, and the influence of large corporations such as Microsoft Corporation, Google LLC, Apple Inc., and Facebook, Inc. (Meta Platforms, Inc.). Debates around features like Proxy semantics, module resolution, and temporal proposals have involved community stakeholders including authors from jQuery, Babel, TypeScript, and independent contributors on GitHub. Critiques have referenced processes compared to W3C and IETF norms, discussions about transparency involving proprietary implementers, and disputes aired at events like Paris JavaScript Meetup and JSConf. Legal and patent concerns have occasionally involved counsel from organizations such as Oracle Corporation and IBM in standards deliberations.

Category:Standards organizations