Oracle inherited the trademark for "JavaScript" from Sun Microsystems, producing legal risk when the name is used to describe work, products, or events. The language was originally called Mocha, then LiveScript, and later JavaScript; trademark constraints forced the official standard to use the name "ECMAScript." The trademark obstructs straightforward use of the common name, discourages renaming the standard, and creates uncertainty for conferences and products. Potential remedies include forcing Oracle to relinquish the trademark through legal action or adopting a new name, though renaming conflicts with established conventions like the .js filename extension.
During its lifetime, JavaScript has had several names: During development, its name was Mocha. In the Netscape Navigator 2.0 betas (September 1995), it was called LiveScript. In Netscape Navigator 2.0 beta 3 (December 1995), it got its most common name, JavaScript. Why that name? JavaScript was going to be a glue language for components written in Java. The first standard for JavaScript was published in 1997, hosted by Ecma International (called ECMA at the time).
How can we improve the current situation? # Solution: forcing Oracle to give up the trademark # Deno currently sues Oracle to force them to relinquish their trademark. They are currently asking for donations to help them with that effort. If that effort succeeds then two things will change: Using the term "JavaScript" would not be legally risky anymore. "ECMAScript" could be renamed to "JavaScript standard".
Collection
[
|
...
]