News for hackers. Stuff that matters.
Re:Tips for Performant TypeScript by nicoburns on Tuesday November 24, 2020 @10:31AM (#25199330)
Deno still compiles it to JS. It just does it for you.
Re:Tips for Performant TypeScript by capableweb on Tuesday November 24, 2020 @12:13PM (#25200480)
Which at one point gets compiled to machine code. At one point, you have to stop and say, "Yeah, this does effectively runs TypeScript", otherwise as I said, you'll end up saying nothing gets run but machine code. While that's correct, not very useful.
Re:Tips for Performant TypeScript by nicoburns on Tuesday November 24, 2020 @12:17PM (#25200523)
I think the key point in this case is that the performance characteristics of Deno don't significantly differ from TypeScript independently transpiled to JavaScript and run in Node because the compilation pipeline is more or less the same (Deno is using tsc and v8 internally)
Re:Tips for Performant TypeScript by ulucs on Tuesday November 24, 2020 @01:06PM (#25201098)
I think the distinction will hold when you can access type information at runtime
Re:Tips for Performant TypeScript by ragnese on Wednesday November 25, 2020 @03:01PM (#25213617)
Why? Haskell doesn't even have runtime type information. So what would you call the stuff that runs after I compile my Haskell code? Not-Haskell?