Creator Of Deno vs Oracle

A trademark cancellation fight over the term “JavaScript” is moving forward, with Oracle filing a motion to dismiss after receiving a petition from the Deno project’s creator. The dispute matters because it targets whether “JavaScript” functions as a generic name for a technology used across many products—or whether Oracle can keep exclusive trademark control despite having no direct product tied to the term.

The core background is that Oracle owns the “JavaScript” trademark through its acquisition of Sun Microsystems, which had a partnership with Netscape in the late 1990s. That ownership has long surprised developers, especially since the trademark standard is formally referred to as “ECMAScript,” a naming choice intended to avoid trademark entanglements. The practical effect is an atmosphere of uncertainty: even when companies build runtimes, tools, or books that use “JavaScript” in their branding, they may worry about future legal pressure.

The petition for cancellation, filed by the Deno-side effort, includes three main claims. First, “JavaScript” is argued to be generic—describing a language used by many implementations rather than a single source-identifying product. The petition points to multiple engines and implementations (including V8 and SpiderMonkey) and to the open nature of the language.

Second, the petition argues the trademark has been abandoned because Oracle allegedly hasn’t maintained and enforced it in a way trademark law requires. The argument cites the continued existence of millions of “JavaScript” books and materials sold through major retailers that do not describe Oracle products.

Third, the petition alleges fraud in Oracle’s 2019 renewal filing, claiming Oracle submitted evidence that included a screenshot from a project unrelated to Oracle—specifically a “no. js” site—while Oracle later countered with a different screenshot showing “JavaScript” usage on an Oracle website via Oracle JET. The dispute here is less about whether “JavaScript” appears somewhere, and more about whether Oracle’s renewal evidence was accurate and properly controlled.

Oracle’s response so far is described as a motion to dismiss focused on the fraud claim. The petitioners expect months of back-and-forth, including discovery and procedural steps before the Trademark Trial and Appeal Board (TTAB), where the claims will be narrowed and argued. The fraud allegation is treated as the hardest to prove because it requires showing intent, not just error.

Beyond the immediate legal process, the discussion highlights a broader risk calculation: if Oracle ever chose to enforce the trademark aggressively, it could trigger widespread renaming efforts and public backlash across authors, tooling, and educational materials. The speaker argues that Oracle’s incentives likely don’t favor that kind of disruption, especially since Oracle doesn’t appear to sell a product that depends on “JavaScript” as a brand.

The conversation also draws a comparison to TypeScript. The argument is that TypeScript is different because Microsoft created it, controls the primary implementation (TSC), and the trademark situation is tied to a maintained ecosystem. Finally, the creator emphasizes that Deno’s corporate structure provides standing to bring the case, and notes that legal costs may rise during discovery, with a call for people to sign an open letter at javascript.tm to build awareness and support.