[flagged]
A 10x Faster TypeScript
211–220 of 943 posts
Re: A 10x Faster TypeScript
#212Any plans for a AOT version of Typescript with strict typing that targets WASM or LLVM?
Re: A 10x Faster TypeScript
#213Hi folks, Daniel Rosenwasser from the TypeScript team here. We're obviously very excited to announce this! RyanCavanaugh (our dev lead) and I are around to answer any quick questions you might have. You can also tune in to the Discord AMA mentioned in the blog this upcoming Thursday.
Have you considered a closer to metal language to implement the compiler in like c or rust ? Have you evaluated further perf improvements ?
I don't think c or rust are really 'closer to the metal' than golang (what they're using)
Re: A 10x Faster TypeScript
#214Earlier quoted context omitted.
> Go and Rust are both memory safe. Go doesn't seem to be memory safe, see https://www.reddit.com/r/rust/comments/wbejky/comment/ii7ak8... and https://go.dev/play/p/3PBAfWkSue3
I love Rust, but you can play exactly the same game with Rust: https://github.com/Speykious/cve-rs
I mean, no? That's basically a known bug in Rust's compiler, specifically it's a soundness hole in type checking, and you'd basically never write it by accident - go read the guts of it for yourself if you think you might accidentally do this.
At some point a next generation solver will make this not compile, and people will probably invent an even weirder edge case for that solver.
Whereas the Go example is just how Go works, that's not a bug that's by design, don't expect Go to give you thread safety that's not what they promised.
Re: A 10x Faster TypeScript
#215Earlier quoted context omitted.
I don't think it's misleading at all, because you can't run Typescript. Typescript is either compiled, transpiled or stripped down into another language and that's what gets run in the end.
You could make the same argument of anything but bytecode and even then some would debate if it's really running directly enough on modern CPUs. In the end it still remains that you have the time it takes to build your project in a given language and the runtime performance of the end result. Those remain very useful distinctions regardless of how many layers of indirection occur between source code and execution.
The difference here is that with Typescript, you're not really measuring Typescript's performance, but whatever your output language is. If transpile to Javascript, you're measuring that, if you output Wasm, you measure that, etc, and the result isn't really dictated by Typescript.
Re: A 10x Faster TypeScript
#216Earlier quoted context omitted.
This is a great response but this is "why is Go better than JavaScript?" whereas my question is "why is Go better than C# , given that C# was famously created by the guy writing the blog post and Go is a language from a competitor?" C# and TypeScript are Hejlsberg's children; C# is such an obvious pick that there must have been a monster problem with it that they didn't think could ever be fixed. C# has all that stuf…
Anders answers that question here - https://www.youtube.com/watch?v=10qowKUW82U&t=1154s Transcript: "But I will say that I think Go definitely is much more low-level. I'd say it's the lowest level language we can get to and still have automatic garbage collection. It's the most native-first language we can get to and still have automatic GC. In contrast, C# is sort of bytecode-first, if you will. There are some ahead…
A missed opportunity to improve c# by dogfooding it with TS compiler rewrite.
Re: A 10x Faster TypeScript
#217Too bad they didn’t choose Rust, would have loved contributing (not picking up Go, sry)
did you contribute to the current TypeScript codebase? (not intended snarky, just curious)
a couple of commits merged yrs back, things I stumbled on that I used as an excuse to learn more about internals
Re: A 10x Faster TypeScript
#218Earlier quoted context omitted.
Amazing news, but I'm wondering what will happen to Monaco editor and all the SaaS that use typescript in the browser?
Not sure if it does but the video linked in the post might answer your question? I think he is compiling vscode which includes Monaco editor which is where they are getting 10x faster stat. (I might be wrong here.) [0] [0] https://youtu.be/pNlq-EVld70?feature=shared&t=112
Yeah I saw that but will they maintain a browser compatible version is another question
Re: A 10x Faster TypeScript
#219Earlier quoted context omitted.
I don't think it's misleading at all, because you can't run Typescript. Typescript is either compiled, transpiled or stripped down into another language and that's what gets run in the end.
You could make the same argument of anything but bytecode and even then some would debate if it's really running directly enough on modern CPUs. In the end it still remains that you have the time it takes to build your project in a given language and the runtime performance of the end result. Those remain very useful distinctions regardless of how many layers of indirection occur between source code and execution.
Not really in the case of TypeScript, because (with very small exceptions) when you “compile” TypeScript you are literally just removing the TypeScript, leaving plain JavaScript. It’s just type annotations; it doesn’t describe any runtime behavior at all.
Re: A 10x Faster TypeScript
#220Hi folks, Daniel Rosenwasser from the TypeScript team here. We're obviously very excited to announce this! RyanCavanaugh (our dev lead) and I are around to answer any quick questions you might have. You can also tune in to the Discord AMA mentioned in the blog this upcoming Thursday.
When can we just replace the JS runtime with TS and skip the compiler altogether? Start fresh, if you will.