I’ve been following the JavaScript trademark saga closely, and let me tell you - it’s more fascinating than your typical tech legal battle.
Ryan Dahl (creator of Node.js) and Brendan Eich (creator of JavaScript itself) are taking on Oracle over a trademark that’s become as generic as “escalator” or “thermos.”
Having worked with large tech companies, I know their playbook well. Oracle faces a decision that’s more complex than it appears on the surface. While they could fight the petition, release the trademark voluntarily, negotiate some middle ground, or ignore it completely, the real calculation goes deeper than just legal strategy.
Oracle’s history with developer communities tells us everything we need to know about how this might play out. When they acquired Sun Microsystems, they inherited not just JavaScript’s trademark, but also control of Java, MySQL, and OpenOffice. Their handling of these properties followed a pattern: initially aggressive protection of their rights, followed by community backlash, and eventually a more nuanced approach.
The Hudson/Jenkins split particularly stands out in my mind. When Oracle asserted trademark rights over Hudson (a continuous integration server), the community simply forked the project and renamed it Jenkins. Today, Jenkins dominates the space while Hudson is barely remembered. Oracle learned an expensive lesson: in open source, community goodwill often matters more than legal rights.