Live data from Hacker News

It’s time to free JavaScript (2024)

javascript.tm

171–180 of 393 posts

Re: It’s time to free JavaScript (2024)

#172

I actually think that people should rather use EcmaScript name instead of JavaScript, because it's a way better name (much less confusing, given that this lang doesn't have anything to do with Java anyway). I wish Oracle started suing people to force everyone to use the better name.

I think most of us just call it JS now. And we really write mostly TS anyway.

that would be very culturally/industry specific. Personally, I do call it javascript.

Re: It’s time to free JavaScript (2024)

#173
post #62

Earlier quoted context omitted.

Stop spreading defeatism. Either channel these energies into something better, or just get out of the way.

"Defeatism" is yet another shibboleth for people who refuse to accept reality. Wasting your money on things you can't change when you could be spending it on things you can is true "defeatism", as it accomplishes nothing.

You don't understand. They're calling the manager. Everything can be solved by calling the manager.

Re: It’s time to free JavaScript (2024)

#174

Why is this worth doing? What wrong with the status quo? The author does not give any examples of Oracle threatening people for using the JavaScript (tm) name.

The problem is FUD. Some guy at a company gets told he has to wait for legal to approve some open source project or initiative that happens to use JS in the name, because his boss heard there’s a trademark issue, and the enthusiasm fades and the idea gets sidelined. There’s probably been thousands of tiny little instances of FUD like that, which we’d never hear about, and which have led to good things not happening.

One clear instance of FUD we do know about is the spec itself is not titled with the name of the language it specifies, which is then its own source of confusion for newcomers trying to learn the web platform, and makes it harder for old timers to explain things, and is generally annoying. Complexity. Confusion. Doubt. Inaction.

Removing legal FUD from the world is a good cause. I don’t mind if it also works as a good marketing play for Deno.

Re: It’s time to free JavaScript (2024)

#175

Earlier quoted context omitted.

I am going to sound crazy, but, if Microsoft would free up TypeScript and every browser added native TypeScript features to JavaScript… and then we all just started calling it TypeScript. Maybe? Then you would see native ts files. Oracle will never give up JS. The funny thing is the number of people who confuse Java and JS.

From experience, corporations usually don't give the general public any trademarked name. I assume TypeScript is trademarked right now; and I doubt Microsoft would ever liberate this. So in this regard, the corporations act in the same manner - selfish.

TFA says Microsoft offered the JScript trademark to be used in place of JavaScript, so there’s some indication of willingness to give up a trademark.

Re: It’s time to free JavaScript (2024)

#176
post #174

Why is this worth doing? What wrong with the status quo? The author does not give any examples of Oracle threatening people for using the JavaScript (tm) name.

The problem is FUD. Some guy at a company gets told he has to wait for legal to approve some open source project or initiative that happens to use JS in the name, because his boss heard there’s a trademark issue, and the enthusiasm fades and the idea gets sidelined. There’s probably been thousands of tiny little instances of FUD like that, which we’d never hear about, and which have led to good things not happening.…

This! I dont think people realize how many people fold like this. Almost nothing actually gets litigated. Litigation is a huge risk and very expensive. The profit incentive at companies means this fight is almost never worth it and its just easier to fold and use a competitor's technology.

Re: It’s time to free JavaScript (2024)

#179

I actually think that people should rather use EcmaScript name instead of JavaScript, because it's a way better name (much less confusing, given that this lang doesn't have anything to do with Java anyway). I wish Oracle started suing people to force everyone to use the better name.

> because it's a way better name (much less confusing, given that this lang doesn't have anything to do with Java anyway). Probably if we were in the early 2000s this could have been a battle worth fighting. But considering we're in 2025 and probably more people are aware of JavaScript than Java at this point, even when you're deep in enterprise-land, I'm not sure it'd be less confusing. Anyways, you're about two dec…

From days of old...

Invoking Applet Methods From JavaScript Code - https://docs.oracle.com/javase/tutorial/deployment/applet/in...

and

Invoking JavaScript Code From an Applet - https://docs.oracle.com/javase/tutorial/deployment/applet/in...

Aside from the "Java is cool, name everything Java" in the early days - there was scripting between the browser and the applet using a language named JavaScript.

Re: It’s time to free JavaScript (2024)

#180
post #74
post #24

Earlier quoted context omitted.

The irony is I belive the JavaScript creator wtnted to latch to Java's popularity to called it JavaScript and now both Java and JavaScript are owned by Oracle and they want the name but not want to change is to ECMAScript, it's real official name.

If you read the original JavaScript press release ( https://web.archive.org/web/20020808041248/http://wp.netscap... ), it's mainly intended as a language to write glue code so Java applets (where the real application logic would go) can interact with a webpage: > With JavaScript, an HTML page might contain an intelligent form that performs loan payment or currency exchange calculations right on the client in response…

The story is somewhat more complicated than that and not amenable to a simple summary, because there are multiple entities with multiple motivations involved. Keeping it simple, the reason why the press release babbles about that is that that is corporate Netscape talking at the height of the Java throat-forcing era. Those of you who were not around for it have no equivalent experience for how Java was being marketed back then because no language since then has been backed by such a marketing budget, but Java was being crammed down our throats whether you like it or not. Not entirely unlike AI is today, only programmers were being even more targeted and could have been seeing more inflation-adjusted-dollar-per-person spend since the set of people being targeted is so much smaller than AI's "everyone in the world" target.

This cramming did not have any regard for whether Java was a good solution for a given problem, or indeed whether the Java of that era could solve the problem at all. It did not matter. Java was Good. Good was Java. Java was the Future. Java was the Entire Future. Get on board or get left behind. It was made all the more infuriating for the fact that the Java of this time period was not very good at all; terrible startup, terrible performance, absolutely shitty support for anything we take for granted nowadays like GUIs or basic data structure libraries, garbage APIs shoved out the door as quickly as possible so they could check the bullet point that "yes, java did that" as quickly as possible, like Java's copy-of-a-copy of the C++ streaming (which are themselves widely considered a terrible idea and an antipattern today!).

I'm not even saying this because I'm emotional or angry about it or hate Java today. Java today is only syntactically similar to Java in the 90s. It hardly resembles it in any other way. Despite the emotional tone of some of what I'm saying, I mean this as descriptive. Things really were getting shoveled out the door with a minimum of design and no real-world testing so that the Java that they were spending so much marketing money on could be said that yes! It connected to this database! Yes! It speaks XML! Yes! It has a cross-platform GUI! These things all barely work as long as you don't subject them to a stiff breeze, but the bullet point is checked!

The original plan was for Java to simply be the browser language, because that's what the suits wanted, because probably that's what the suits were being paid to want. Anyone can look around today and see that that is not a great match for a browser language, and a scripting language was a better idea especially for the browser in the beginning. However, the suits did not care.

The engineers did, and they were able to sneak a scripting language into the browser by virtue of putting "Java" in the name, which was enough to fool the suits. If my previous emotional text still has not impressed upon you the nature of this time, consider what this indicates from a post-modern analysis perspective. Look at Java. Look at Javascript. Observe their differences. Observe how one strains to even draw any similarities between them beyond the basics you get from being a computer language. Yet simply slapping the word "Java" on the language was enough to get the suits to not ask any more questions until much, much later. That's how crazy the Java push was at the time... you could slip an entirely different scripting language in under the cover of the incredible propaganda for Java.

So while the press release will say that it was intended to glue Java applets, because that's what the suits needed to hear at that point, it really wasn't the case and frankly it was never even all that great at it. Turns out bridging the world between Java and Javascript is actually pretty difficult; in 2025 we pay the requisite memory and CPU costs without so much as blinking but in an era of 32 or 64 MEGAbyte RAM profiles it was nowhere near as casual. The reality is that what Javascript was intended to be by the actual people who created it and essentially snuck it in under the noses of the suits is exactly what it is today: The browser scripting language. I think you also had some problems like we still have today with WASM trying to move larger things back and forth between the environments, only much, much more so.

We all wish it had more than a week to cook before being shoved out the door itself, but it was still immensely more successful than Java ever could have been.

(Finally, despite my repeated use of the term "suits", I'm not a radical anti-business hippie hacker type. I understand where my paycheck comes from. I'm not intrinsically against "business people". I use the term perjoratively even so. The dotcom era was full of bullshit and they earned that perjorative fair and square.)

Post reply on HN