Summary

  • ECMA-262 received General Assembly approval in June 1997; TC39 chose the name ECMAScript at its September meeting.
  • The fifth-meeting minutes say JavaScript and LiveScript were unavailable as standard names. The first edition kept JavaScript in its history as an originating technology.

Analysis

The browser shipped before the committee finished naming the standard

The committee’s name problem arrived after the software. Brendan Eich later recalled that the engine prototype took ten days in May 1995; browser integration occupied the rest of that year. On 4 December, Netscape and Sun announced JavaScript and said its initial version was already available in the beta of Netscape Navigator 2.0. The release pitched a cross-platform scripting language for applications on enterprise networks and the Internet. The product had a browser home before it had a standards-body title.

The sequence matters. A browser feature can work inside one product while its public name belongs to a company’s commercial vocabulary. A shared standard asks for another kind of name: one that describes a common language and travels across implementations. The two jobs touched the same code and answered to different constraints.

The first public announcement already pointed toward that second job. Netscape and Sun said they planned to submit JavaScript to standards groups. Ecma’s later record shows TC39 began work in November 1996. Its chair’s report lays out a fast schedule: first draft in January 1997, General Assembly vote in June, and acceptance of the standard’s name in September. The specification advanced while the label stayed open.

That gap is easy to miss because the first edition of ECMA-262 carries June 1997 on its cover and uses ECMAScript in its title. Ecma’s later account explains the sequence: the General Assembly approved the technical text in June, while some editorial matters, including the final name, remained for September. The title printed on the finished document compresses those decisions into one clean cover. The meeting record shows the paperwork underneath it.

Agenda item five was a trademark problem

The minutes of TC39’s fifth meeting, held on 16 and 17 September 1997, reserve a section for the standard’s title and the language’s name. The record is unusually blunt: JavaScript and LiveScript were unavailable. The group chose ECMAScript unanimously. The chair’s report says the name discussion involved trademark impact; the minutes ask Netscape to provide information about the conditions for using JavaScript.

That is a narrow fact with a large consequence. The committee could standardize syntax and semantics, but it could not assume that a company’s product name was free for a neutral, cross-platform specification. ECMAScript gave the standard a title the committee could use. The product label remained JavaScript.

The June and September documents also explain why the first edition can carry a June date while Ecma says the final name was decided later. June records approval of the standard text. September records the choice of its title. A standard has more than one finish line; the cover makes them look like one.

A standard name and a product name did different work

The first edition’s brief history lists JavaScript among the technologies from which the standard was drawn. Ecma’s 2017 retrospective says ECMAScript and JavaScript are both used for the same standard in practice. The names did not mark two unrelated languages. They separated a standards document from a product identity.

That separation is useful. Implementers can point to a neutral specification without obtaining ownership of the most familiar label. Writers and developers can keep saying JavaScript, the name that reached the browser beta and its users. The standard records a common technical contract; the product name carries the memory of where the feature arrived.

The code was running first. The institution followed by describing behavior that could be shared across platforms. Then the standards process met a boundary that code alone could not settle: who could use the name on the document. The result sounds like a committee’s compromise because it was a committee’s answer to a real constraint. For years, one language has answered to two names, each doing a different job.

The public record establishes that the names JavaScript and LiveScript were unavailable for the standard and that trademark issues shaped the choice. It does not preserve the terms or cost of a possible license; a licensing record would show whether ECMAScript was a forced route or a preferred one.

Sources

Sources