tolmasky
5 days ago
In all seriousness, let's just rename it "WebScript". WebAssembly, WebGPU, WebRTC, WebWorkers. It fits. And it seems like there's no active trademark for it too (although I admittedly did not do a super sophisticated search).
The “Java” prefix still confuses new users, not to mention "bizdev" people, and probably leads to legal issues beyond just the trademark. "JavaScript" has always sucked as a name, we're just used to it now. Why are we fighting so hard for it? Let's just take this as an opportunity to name it something that actually makes sense. It will maybe be sort of annoying for a few years, but I'm certain one day we'll look back and not believe we used to call it "JAVA Script".
tolmasky
5 days ago
It occurs to me that "WebScript" actually solves another tricky problem: describing the thing people mean when they say JavaScript, vs. the thing JavaScript actually, technically, is. You see, technically, JS doesn't have half the functionality you're used to, like WebSockets, TextEncoder, fetch, or even something as simple as the URL class. In fact, JS does not technically even "fully" support ESM modules, as major portions of that standard are delegated to other Web Platform APIs.
There's good reasons for all of this of course, but from an end user perspective, it's pretty confusing that URL is not part of JS but encodeURIComponent is. And Uint8Array is part of JS but TextEncoder isn't. But the cool thing is that increasingly no one needs to worry about that because the non-browser JS runtimes have settled on the idea that they should implement the Web Platform APIs. So as a developer, you can just act as if WebSockets is part of JavaScript.
But there's no good name for this “collection" of standards that are together commonly accepted to be "JavaScript". No one says "JavaScript with browser-compliant modules and WebWorker additions…”, and even saying “ECMAScript with the Web Platform Additions” is a mouthful. But you know what does convey “ECMAScript, the way you're used to it in browsers”? WebScript.
This very much makes the case for not using ECMAScript, since ECMAScript still has a separate meaning. It is the pure language spec. Useful as a term for spec writers, pedantic everywhere else. Meanwhile, "WebScript" formalizes what people were sometimes (but not always) bending "JavaScript" to do before, and thus actually does add "new utility" to the terminology, vs. just being a replacement synonym that avoid legal issues.
HelloImSteven
4 days ago
WebScript is trademarked by Apple [1], but not sure how enforceable it is at this point.
[1]: https://www.apple.com/legal/intellectual-property/trademark/...
tolmasky
4 days ago
It shows up as dead on on uspto: https://tsdr.uspto.gov/#caseNumber=75300777&caseSearchType=U...
SwiftyBug
5 days ago
We should just use ECMAScript. A big part of the ecosystem uses the terms esm, es5, es6, esnext, etc.
tolmasky
5 days ago
To be clear, I'd be fine with this, I just think it wouldn't catch on. It's just an awkward name, that exists for this same trademark reason, and was thus never expected to take on "marketing" duties (sort of like calling WebWorkers W3CWorkers instead).
This is of course speculation, but I think people would interpret us trying to switch to "ECMAScript" as a sort of sulky defeat "wait so we're just going to let Oracle have JavaScript and just use the soulless spec name? No way, we should fight for JavaScript!" It feels like we're "settling" for the SKU number since we lost the name (again, due to the uniquely bizarre, but understandable in context, spec name).
In other words, besides the "consistency" that WebScript offers (WebWorkers, WebGPU, etc.), the other thing it brings to the table is just being something new and different. "Hey! Let's move on from this whole debacle, here is a symbolic thing that represents a new chapter, with zero associated baggage." I am largely basing this off of the experience of "html5," which arguably addressed a similar non-technical debacle in the form of the W3C/WHATWG drama. It is surprising how effective a new name can be at putting a positive spin on things.
Again, I personally have no issue with ECMAScript, I just think the boat has sailed on getting people to switch to that, and if we switch to anything, the goal should be to make sure to get everyone onboard.
0manrho
4 days ago
Fully agreed on all points. I'm fine with either, but now is the time to change all considered. Personally I prefer ECMAscript as I already have a familiarity there, but you make an excellent point about webscript being a better general and beginner/outsider friendly term.
jasonm23
4 days ago
tl'dr WebScript good, sticky / recognizable,
and my addition: Oracle / JavaTM should as always, go away and kick rocks
mr_toad
5 days ago
That’ll confuse the hiring managers and recruiters.
“Your CV says that you use JavaScript/WebScript. Which one would you say you used most often?”
tolmasky
5 days ago
You’re thinking about it like a bug instead of a feature. When HTML5 was announced everyone expected it on your resume like every other buzzword. WebScript should be pitched like that: the hot new thing. Managers won’t be confused (or rather, no more confused than usual), they’ll be excited. And for the first time in tech history, people will actually have 5 years experience in a technology that was announced this year.
zeroq
5 days ago
Reminds me of that one recruiter:
- I need to run a quick survey on your tech, ok?
- But you have my CV, it should be rather obvious if I fit or not. Doh. Whatever.
- Perfect. How many years of experience you have with JavaScript?
- Dude, really? ... I don't know, I've been using it since '99.
- Perfect. More than 3 years it is. Onto the next question!
egorfine
5 days ago
Oh, I mostly use ECMAScript these days.
lkirkwood
5 days ago
This is a funny thought, but do you think this would really happen? Surely anyone hiring a programmer would be aware of this.
komali2
5 days ago
Oh, gosh, when was your last job hunt? As of 9 months ago I still heard a "This job requires Java so you'll be a great fit" from a recruiter when he saw JavaScript on my resume.
lkirkwood
4 days ago
Wow that is not encouraging
askonomm
5 days ago
From what I understand of modern hiring practices, the automated systems match for exact keywords, and if WebScript is not in the system, you don't get matched, and no actual human will even see your resume.
undefeated
5 days ago
Surely you've never read the job description for a programming position
dudeinjapan
5 days ago
Oh no! Anyway…
donatj
5 days ago
I was going to suggest just going back to it's original name of LiveScript but it looks like that was subsumed by a language from the creator of CoffeeScript. How rude.
Early in my career, in the early 2000's I was tasked with modernizing a massive site that had many <script type="application/livescript"> tags throughout. I still don't fully understand, was it released to the public under this name at some point?
My googling just now indicates there may have been just a single public beta of Netscape that called it that. How strange.
jampekka
5 days ago
I don't think the creator of CoffeeScript (Jeremy Ashkenas) was (directly) ever involved in LiveScript. LiveScript was forked from Coco which was forked from CoffeeScript.
Wikipedia does claim Ashkenas was involved [1], but LiveScript website doesn't list him [2].
[1] https://en.m.wikipedia.org/wiki/LiveScript_(programming_lang... [2] http://livescript.net/#thanks
andyferris
5 days ago
I mean... did Oracle consult the government in Jakarta about their use of the term Java? There are more than 100 million people there and we squabble about the conotations of the name of a programming with the name of another programming language whose name has connotations about someone elses island which is actually a connotation about some coffee some programmers drank who felt Jolt Cola is so Microsoft and isn't as cool as freshly roasted beans anymore (...in 1996).
But WebScript I could actually get behind! (if the case fails)
tolmasky
5 days ago
I agree that Oracle's case has no merit, for all sorts of reasons. But the time investment is asymmetric. It is easy for them to drag their feet, it is easy for them to confuse the judge who is almost certainly unfamiliar with the bizarre naming history of this language, and they have nothing better to do. Oracle can throw 100 interchangeable lawyers at this. Meanwhile, this is sucking the time of unique individuals like Ryan Dahl. It is a tragedy that his attention should go to this.
But this is especially so given that JavaScript isn't even a good name. It would be one thing to fight this on principle if the name was great, but it isn't. In fact, the name was specifically originally chosen due to its confusion-causing powers -- the unfortunate reality is that JavaScript was chosen precisely to ride the coattails of the then hot new technology Java. This was a horrible idea from day one. No one would suggest I name a new unrelated programming language "SwiftScript" or "RustScript" today to benefit from the popularity of those languages. It would be both tacky and shortsighted. Is it tacky enough to change in isolation? No, it would just be yet another unfortunate part of tech culture, like "referer" only having 3 r's instead of 4. But it absolutely is tacky enough to give up if we are facing some huge case against an actor that is quite literally infamous for their stubbornness in court. No one at Oracle is thinking about this for longer than 5 minutes, while it is causing tremendous grief to Ryan and half the JavaScript community. Why give them that? Let Oracle own all the shitty Java-related trademarks. We're not even handing them a win. The JS trademark will become worthless once we all switch to WebScript, and as an added bonus it won't even accidentally provide even a tiny bit of free marketing for any other their technologies like JavaScript maybe does today. Their reward can be a step further toward of obscurity, self-excising themselves from their current unearned appearance in the history of the web whenever JavaScript is mentioned.
wltr
5 days ago
So much this! About 20 years ago, when I only started dealing with JS, I couldn’t grasp that pathetic name. Why even have Java in there?
Personally, I so much hate these so much weird nerdy stupid names. Gimp, anyone? These recursive acronyms like GNU, does somebody actually think that’s funny?
Count me in, I like web script.
welder
4 days ago
Renaming it on GitHub.com in this PR:
ghurtado
4 days ago
> In all seriousness, let's just rename it "WebScrip...
This has approximately the same chances of success as the rebranding of Twitter
jagged-chisel
4 days ago
So you’re saying there’s a chance
pjmlp
4 days ago
Just like WebAssembly running on Cloudflare, or WebGPU on Bevy, have anything to do with Web browsers.
chipsrafferty
4 days ago
Also, who cares about the trademark? JS devs should not care, really