zlacker

>>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.

>>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.

>>gianca+cD
For years we said bring something sane to browsers instead of trying to salvage js. At this point, though, why don't they just implement DOM bindings in wasm and make internets a better place overnight?

>>friend+8Q
TypeScript is a really decent language though, I wouldn't feel happier or more productive using Fortran or whatever. Its type system is actually really powerful which is what matters when it comes to avoiding bugs, and it's easy to write functional code with correct-by-construction data. If you need some super optimized code then sure that's what WASM is for but that's not the problem with most web apps, the usual problem is bad design, but then choice of language doesn't save you. Sure TS has some annoying legacy stuff from JS but every language has cruft, and with strict linting you can eliminate it.

It's also better if there's one ecosystem instead of one fragmented with different languages where you have to write bindings for everything you want to use.

>>chpatr+e41
Its type system is also full of holes because it has to be compatible with JavaScript, being a superset.