241–250 of 374 posts
Earlier quoted context omitted.
Sure, let me just rename all of my file extensions and parsers to .ws and then handle the collisions with websockets paths and then revert it all back to how it was before I touched anything
Sounds really like a development environment problem, I mean if you can't handle that your language suddenly changes it's name in a not backward compatible fashion, how do you ever stand a chance to handle leap seconds correctly?
Most code doesn't need to handle leap seconds at all.
Surprised by the amount of mentions of ECMAScript here. It’s the worst possible name to me.
ECMAScript comes from the spec for JavaScript, which makes sense.
Earlier quoted context omitted.
I want Deno to succeed. They already have enough challenges between bun and Node taking all of their good ideas and incorporating them. I want the ecosystem to have more options. This is Oracle we are talking about here. I would cut off my nose to spite Oracle’s face if necessary, they are some of the worst corporate actors in the history of the world. And that is not an exaggeration.
I also desperately want deno to succeed cause it’s just the best way to work with typescript. I have a strong personal interest in working with deno instead of node in the future. At my company a lot of internal stuff is built with deno. Nothing mission critical but lots of utilities and stuff. But new services are still node, which is basically fine cause all of the complex config is handled already. But all of that…
My life is much better for having switched to vitest
I appreciate the thought but this isn’t even a David and Goliath .. this is David’s infant taking on Goliath… Oracle spends more on lawyers than engineers. If this 200k is spent it will be thrown in the garbage. Unless Oracle wants to release it on their own they’ll happily stay in court until every penny Deno has is gone and not think twice about it. Have the team focus on something else.. this isn’t even worth typi…
The name "JavaScript" was silly to begin with, just a way to make the buzzword "Java" more popular. Let's call it WebScript and move on.
Why not “JS”? Then we can all take sides in a religious war on whether it’s pronounced jay-ess, jayce, juss, or jess?
You also couldn’t call it Jscript because Microsoft owns the trademark there.
EMCAScript is the most practical from a legal standpoint, but that name sucks badly.
The name "JavaScript" was silly to begin with, just a way to make the buzzword "Java" more popular. Let's call it WebScript and move on.
We can also call it ECMAScript. I always try to refer to it as ES instead of JS in professional coding context.
For "WebScript" that works. Even just "JS" works. For "ECMAScript" not so much.