Essentially the same html/css rendering of Firefox or Chromium, still able to access the www, but with javascript fully removed for another language that can be interpreted - like python or lua. Is this feasible?
Essentially the same html/css rendering of Firefox or Chromium, still able to access the www, but with javascript fully removed for another language that can be interpreted - like python or lua. Is this feasible?
I dunno, I don’t see the benefit to native TS in the browser. For compatibility, all sites will continue to serve JS, so what does TS gain anyone? And there is no performance benefit, maybe a performance hit given none of the type validation can happen until all of the scripts have downloaded, so execution can’t begin until that has happened?
I could be way off on this though, I’m not a webdev :/
Type assertion in runtime would be really useful
Can you even get runtime type assertions in TS? Isnt it all at compile time?
That’s my point… You’d need native TS support for that
I don’t think I understand. Native TS does the type checking at compile time right? Not run time? Or would the compile happen in the browser?
Browser-native TS would run directly on the browser without compiling.
At least in the node.js native TS implementation, they strip the types and don’t do checks, so you don’t get runtime type checks:
https://nodejs.org/learn/typescript/run-natively
I think, but I’m no expert, but in order to have type checking you need to have some kind of compilation check? You cant just start interpreting and hope to work things out on the fly?