zlacker

[return to "It’s time to free JavaScript (2024)"]
1. siwata+Yc[view] [source] 2025-12-04 10:58:11
>>pavela+(OP)
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.
◧◩
2. gianca+cD[view] [source] 2025-12-04 14:08:02
>>siwata+Yc
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.
◧◩◪
3. Vinnl+5E[view] [source] 2025-12-04 14:12:36
>>gianca+cD
An important feature of TypeScript is identifying problems in your code before the user runs it, i.e. before a browser even comes into play.
◧◩◪◨
4. array_+NO[view] [source] 2025-12-04 15:10:38
>>Vinnl+5E
No runtime type safety bites people often and in unexpected ways. It should just be standardized.
◧◩◪◨⬒
5. Vinnl+8Y[view] [source] 2025-12-04 16:04:40
>>array_+NO
Sure, but that's an orthogonal concern. That sounds more like a call to standardise Zod.
[go to top]