101–110 of 393 posts
1) Put JS in maintenance mode, don’t add any language features, only runtime 2) TS becomes the official mainline, whoever doesn’t like types can just keep writing as they did before, because valid JS is valid TS Problem solved, it’s not that difficult.
TS trademark is owned by Microsoft. That would be a case of out of the frying pan into the fire. Not really better.
It's caused way too much confusion over the years making people wrongly associate it with Java. My guess would be that associations exactly why Oracle doesn't want to give it up.
I would like to say go back to the original name of LiveScript from before Netscape tried to woo Sun, but the name LiveScript has been co-opted.
Something else with a J would probably be the least painful. JScript is permanently associated with Microsoft's terrible IE implementation. I offer up "JaScript" as it sounds largely like JavaScript but said with a drawl while retaining "JS".
Heck, I'll call it ECMAScript if that's what it takes. I'd rather not, but it's better than "JavaScript"
They now have GoFundMe where they are soliciting donations for a discovery phase of a patent trademark cancellation request. They have just 50k USD out of 200k USD they are raising. (No idea if that's appropriate; from the outside, it seems like a lot of money, but also they are fighting Oracle which has unlimited money, so, yeah) For some reason it's not linked in the page itself. https://www.gofundme.com/f/help-us-…
Not to nit-pic, but it's a Trademark cancellation - not a patent. The confusion probably came from the fact it's before the US Patent and Trademark Office.
Earlier quoted context omitted.
TS trademark is owned by Microsoft. That would be a case of out of the frying pan into the fire. Not really better.
Call it ES2026 officially and let other people devalue MS' trademark as they refer to that (and later versions) as TS.
Earlier quoted context omitted.
TS trademark is owned by Microsoft. That would be a case of out of the frying pan into the fire. Not really better.
Same as Go and Google then. Is the ownership of the trademark of the name/logo of a FOSS language really that big a deal?
Earlier quoted context omitted.
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…
> Of course over time everyone abandoned applets because of all the security problems, Haha, or because it froze the whole browser for a few seconds upon loading. Unlike Macromedia Flash by the way.
Of course 100% of that cpu is probably 1/10 of one core on any of my modern machines, so an ordinary and not-broken ad laden page routinely eats several times as many cycles now. Progress!
Earlier quoted context omitted.
Call it ES2026 officially and let other people devalue MS' trademark as they refer to that (and later versions) as TS.
...and we'll have another API warfa^H^H^H^H lawsuit that we had for Java.
Earlier quoted context omitted.
They have linked to an example from one of the blog posts: https://www.reddit.com/r/programming/comments/14vnipl/rust_f...
The example is indeed two years old. I also couldn't find any point in the article that explains why this is worth doing.
Someone just wanted to share their Rust + JavaScript knowledge with people, and they got a cease and desist. It's clearly not ideal.
Earlier quoted context omitted.
> 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…
> probably more people are aware of JavaScript than Java at this point All the same, I probably get as many calls from recruiters to fill Java positions as I do JS positions. I've never used the former, and explaining it is always awkward!
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.
EcmaScript just sounds icky.