This article makes for an interesting read. Here follow two early paragraphs for context:
Oracle controls the JavaScript trademark because in 2009 it acquired Sun Microsystems, which applied to trademark the name with the US Patent and Trademark Office back in 1995. The trademark was granted in 2000.
While the database giant does not use the name for any commercial products, its ownership of the trademark has led JavaScript-oriented organizations such as events biz JSConf to adopt branding that avoids the term. As the signatories to the letter observe, the world’s most popular programming language therefore can’t have a conference that mentions what it’s about.
Toward the end, the article mentions an initiative to legally pursue Oracle for trademark abandonment.
Just call it Ecmascript and be done with it. The name JavaScript was misleading from the beginning. Well, Ecma sounds like a skin disease but who cares.
Writing it also feels as nice as a skin disease so it’s fitting well.
Meh, after ECMAScript 2015, most complaints about JavaScript rely on literally old methodologies and syntax.
A lot of complaints come across like complaining about Java because it doesn’t have generics or arrow functions.
Ecmascript is classic, but WebScript might be better going forward.
SmegmaScript is just too close
SmegHeadScript
“I need some more [input] sanitizer for my eczema script, the console is red and inflamed whenever I check it.”
This is the solution.
All names have problems but this one has the least.
but then we have a massive problem that affects millions of people if we call it EcmaScript. POJO becomes POEO, which violates English. Anyone speaking or writing English is negatively affected by the change from POJO to POEO. We should definitely pay Oracle billions of dollars to avoid confusing people about whether it’s POI-oh or POYO… keep it POJO.
I feel like the modern name for it would be just “Script”.
That’s way too broad. Scripting is a pretty broad concept.