The problem with Typescript - zackoverflow

There’s one big caveat though, and it’s the sheer complexity of the Typescript project. The type checker itself is Typepscript’s largest component and it’s a single 25 ***thousand* ** line file. The project is so big I get the sense that it’s the open source equivalent of a black box. No one besides Microsoft really understands how it works, and even Microsoft themselves have said the project is so complicated that optimizations are blocked by complexity. … The primary problem is `tsc` is slow. Deno has addressed this as the TSC bottleneck, and it’s a result of the fact that Typescript’s type system is inherently complex, and written in JavaScript. Projects like esbuild, swc, or Rome can transpile Typescript incredibly fast, but they simply strip the code of its type information. They can’t typecheck, so our build systems are inevitably blocked by waiting on TSC. This doesn’t just affect us at compilation time, it also affects us at development-time. tsserver can have trouble keeping up with big projects, not to mention the memory requirements of running it. VSCode has good language support for Typescript, and it’s no surprise since it’s made by Micrsoft, but you’ll experience slow downs if using another editor. … It seems Deno and Rome tools are discussing ways to tackle the problem, but they seem far from having something ready. esbuild’s author Evan Wallace has said that type-checking is out of scope for the project. Microsoft says they have no plans to port the Typescript compiler to Rust, and I get the sense that they have a different vision for Typescript.