Literally nobody, outside of formal documents and perhaps pedants, uses that catastrophe of a name.

If you are gonna change the name to anything, change it to js. But also, don’t change the name of the language, especially not to ECMAScript.

no it's not, that's a bureaucratic hoop-jump

Does everyone else pronounce that as "eczema script", too?

"We're now firmly in the TypeScript era. 67% of respondents stated they write more TypeScript than JavaScript code – while the single largest group consisted of people who only write TypeScript."

https://2024.stateofjs.com/en-US/usage/

bun is not faster than node, why do people keep thinking this lmao. v8 runtime is like x4 more performant than spidermonkey which is what bun uses.

Rename it GoScript this time around.

The JavaScript name came out of a cross-licensing deal between Netscape and Sun where Netscape would bundle a copy of the JVM with their browser. Sun needed a way to put the JVM on most Windows users' computers to get developers to write Java software instead of Windows software, and they knew Microsoft wouldn't ship a product that would threaten the Windows platform's domination, so they figured that bundling with Netscape was their next best option. If you read the initial JavaScript press release ( https://www.tech-insider.org/java/research/1995/1204.html ), it's mainly marketed as a way to write glue code to make it possible for Java applets (where the real application logic would go) to interact with an HTML page:

> With JavaScript, an HTML page might contain an intelligent form that performs loan payment or currency exchange calculations right on the client in response to user input. A multimedia weather forecast applet written in Java can be scripted by JavaScript to display appropriate images and sounds based on the current weather readings in a region. A server-side JavaScript script might pull data out of a relational database and format it in HTML on the fly. A page might contain JavaScript scripts that run on both the client and the server. On the server, the scripts might dynamically compose and format HTML content based on user preferences stored in a relational database, and on the client, the scripts would glue together an assortment of Java applets and HTML form elements into a live interactive user interface for specifying a net-wide search for information.

> Java programs and JavaScript scripts are designed to run on both clients and servers, with JavaScript scripts used to modify the properties and behavior of Java objects, so the range of live online applications that dynamically present information to and interact with users over enterprise networks or the Internet is virtually unlimited. Netscape will support Java and JavaScript in client and server products as well as programming tools and applications to make this vision a reality.

> "Programmers have been overwhelmingly enthusiastic about Java because it was designed from the ground up for the Internet. JavaScript is a natural fit, since it's also designed for the Internet and Unicode-based worldwide use," said Bill Joy, co-founder and vice president of research at Sun. "JavaScript will be the most effective method to connect HTML-based content to Java applets."

This was all implemented, and Java applets had full interoperability with JavaScript. Applets could call JavaScript functions, and JavaScript functions could call applet methods. Of course over time people gave up on Java applets and JavaScript became a good enough language to write real application logic directly in it. It's true that JavaScript now has virtually nothing to do with Java, but that wasn't the case initially, and the name has at least some logic behind it.

Just FYI, I was reliably informed that jag did java.util.Date as shipped in JDK 1.0. Ta!