4 ms·
Super skeptical that porting this to a new language is going to have the kind of performance gains they expect ... assuming they want to replicate all of tsc's
by nevir 5y ago
Super skeptical that porting this to a new language is going to have the kind of performance gains they expect ... assuming they want to replicate all of tsc's functionality
- eyelidlessness 5y agoIt’s already proven (esbuild, SWC, Bun) to drastically improve performance of TypeScript’s other responsibility: compilation (tsc doesn’t offer an option for this, but ts-node does, for comparison). And while the type checker is certainly more complex, I have a hard time imagining it won’t show similar improvements in a native language.
- resoluteteeth 5y agoCompiling typescript is basically just stripping the type definitions/annotations and other typescript-specific parts of the syntax out. That's a huge difference from actually type checking it.
- eyelidlessness 5y agoAnd yet, it’s drastically slower in JavaScript than in Go, Rust and Zig. I realize different algorithms will optimize differently between JS and native code, but I sincerely doubt tsc is anywhere near optimal speed.
- lucian1900 5y agoThat's mostly because tsc's parser is used by the JS implementations. Writing a parser for the purpose would achieve performance closer to the other implementations.
- strager 5y agoesbuild, SWC, and Bun are not ports of existing programs.