alt Hacker NewsBecause "it doesn't exist". It's just a layer on top of js, it doesn't have its own runtime, and btw what would supporting ts a the browser level mean? If you want to support a static typed language then you could just compile it down to wasm, if you just want to support types and ignore them at runtime there's an overhead price to pay, or should do runtime type checking? And with which tsconfig? Strict or not?
Replies
VerifiedReports • yesterday at 5:39 PM
All good questions. But... it would simply eliminate a step and result in a single language.
Python supports types and is interpreted, right?
➕ show 2 replies
It is a language, it doesn't matter to what it is downcompiled to be able to be run in a browser.
Its now 13 years old, not a hard language to have a proper runtime for it and it would just get rid of all the npm stuff.
And for the amount of typescript we now have, it would be worth it to have proper native support.