JavaScript vs. Oracle: The Trademark War That Could Reshape the Web

If you’re a developer, you probably don’t think much about who owns JavaScript. It’s just… there, like air, water, or coffee. But here’s the kicker: JavaScript isn’t really “free” in the sense you think. The word itself—literally the name “JavaScript”—is trademarked, and it belongs to Oracle Corporation. Yep, the same Oracle that’s more obsessed with yachts than open-source software.

And no, Oracle didn’t invent it. They don’t maintain it. They don’t guide its future. But thanks to some legal maneuvering that dates back to the 1990s, they can technically sue anyone who tries to use the term commercially without permission.

This bizarre situation has quietly simmered in the background for years, but lately, it’s boiling into a full-blown legal drama, thanks to one developer who decided enough was enough. Let’s rewind the tape.

1995: Brendan Eich, 10 Days, and a Browser War

The JavaScript story starts in 1995. Websites back then were basically fancy pamphlets. Netscape Navigator was the hot browser on the block, and its founder Marc Andreessen had a big idea: make the web interactive.

To do that, Netscape needed a lightweight scripting language inside the browser. The plan? Add Scheme, a Lisp dialect. Scheme had closures, first-class functions, and everything you’d want for a flexible web language.

But then corporate politics showed up. Netscape signed a deal with Sun Microsystems, the company behind Java. And while Java was too heavy for the browser, Sun wanted its shiny new language everywhere. So the Scheme dream died, and a new scripting language needed to be invented—fast.

Enter Brendan Eich. He joined Netscape and, in just 10 days, hacked together a prototype language called Mocha. It blended Scheme’s flexibility, Smalltalk’s object orientation, and Java’s C-like syntax.

Mocha became LiveScript, and then—thanks to a marketing gimmick—JavaScript, designed to ride the hype train of Java. It was never meant to be a subset of Java, but the name stuck.

How Oracle Got Involved

Here’s the twist. While Eich created JavaScript, Sun Microsystems trademarked the name. Not because they built it, but because Netscape and Sun were in bed together at the time. When Netscape collapsed, Sun held onto the trademark.

Fast forward: Sun got swallowed up by Oracle in 2010. And just like that, Larry Ellison’s yacht club owned the world’s most popular programming language.

That’s why you’ll sometimes hear developers talk about ECMAScript instead of JavaScript. The official standard lives under ECMA International, not Oracle. But the word “JavaScript”? That’s trademarked. Which is also why you don’t see “JavaScript Conference” or “JavaScript Magazine” as official events—they’d have to license the name.

Enter Ryan Dahl: The Fight Begins

Fast forward to 2022. Ryan Dahl, the guy who gave us Node.js and later Deno, published an open letter to Oracle. In it, he called the trademark a “dark cloud” over the community and argued the best thing Oracle could do was give it back to the public.

Unsurprisingly, Oracle ignored him.

So Ryan turned up the heat. He launched JavaScript.tm, another open letter with stronger legal arguments. His claim? Oracle hasn’t actually used the JavaScript trademark in any real product. According to U.S. trademark law, if a company doesn’t use a mark in commerce, it can be considered abandoned.

To make things spicier, Dahl accused Oracle of committing fraud when they renewed the trademark in 2019. They had submitted Node.js screenshots as proof of use—even though Oracle has nothing to do with Node. The irony is wild: they used Ryan’s own creation against him.

By late 2024, Dahl and Deno officially filed a petition with the U.S. Patent and Trademark Office (USPTO) to cancel Oracle’s ownership.

Oracle Strikes Back

Oracle didn’t stay quiet forever. They filed a response, denying everything. Instead of Node.js, they pointed to something called Oracle JET—a UI toolkit nobody had heard of—as their proof of using JavaScript in commerce.

The case went to the Trademark Trial and Appeal Board (TTAB), which dismissed the fraud claim, saying the Node.js submission wasn’t “fraudulent” by itself. Oracle didn’t knowingly deceive—they just, well, kind of shoved random JavaScript-related stuff into the filing.

Still, the battle isn’t over. Oracle continues to argue that JavaScript isn’t generic, that the trademark hasn’t been abandoned, and that they have the right to keep it.

What Happens Next?

As of August 2025, the case is moving into discovery—the phase where both sides gather evidence, argue over documents, and prepare for trial. The timeline looks something like this:

  • 2025–2026 → Both sides collect evidence and line up arguments.
  • Summer 2026 → The case is presented with closing arguments.
  • Late 2026 / Early 2027 → A final decision is expected from the USPTO.

So, yeah. We won’t know until at least 2027 whether “JavaScript” will be freed from Oracle’s grip.

Why This Matters (Even If You Don’t Care About Lawyers)

At first glance, this might feel like nerd drama. Who cares who owns the name? Code still runs the same, right?

But trademarks can shape ecosystems. Imagine if Oracle decided to aggressively enforce ownership. Conferences, newsletters, libraries, even companies branding themselves as “JavaScript-first” could be forced to change names or pay licensing fees.

It’s not just about words—it’s about control. And in a world where open-source powers the internet, seeing one of the most important languages tethered to a corporation that doesn’t even maintain it feels… wrong.

Ryan Dahl’s fight isn’t just a legal battle; it’s a symbolic stand for developer freedom.

The Bigger Picture

JavaScript is everywhere: powering your favorite web apps, running on servers, embedded in IoT devices. It’s the closest thing the internet has to a universal language.

But the fact that its name is tied up in legal red tape is a reminder that corporate fingerprints are still all over the foundations of the web.

Whether Dahl wins or loses, the case is exposing a deeper truth: the community built JavaScript, not Oracle. And maybe, just maybe, it’s time for the name to belong to the community too.

Stay tuned—the battle for JavaScript isn’t over yet. And whether you’re team Ryan, team Oracle (hi Larry), or just team “I want to write my code in peace,” this story is proof that the web’s history is far messier than we think.

Stay on track with more untangled tech sagas at LaunchPerk Magazine!