News for hackers. Stuff that matters.
Re:TypeScript team released an explorer for performance tuning by rektide on Saturday May 13, 2023 @11:08AM (#35929097)
I just have such a hard time imagining how the other type checkers keep parity.

TypeScript doesn't evolve super fast, but there are a steady stream of great improvements. I'd be so afraid I have either less type checking, things that silently pass/aren't checked, or intelligence that TypeScript has that other checkers don't have.

Also, as others say, just using --watch largely eliminates the problems of using tsc. I haven't worked on any truly huge codebases but it's been quite snappy. It's a longshot, but I wish TypeScript would also be it's own LSP too.

I definitely did love love love how blazingly fast & super easy to work with, no setup, Deno was. Incredibly refreshing, no ceremony.

Re:TypeScript team released an explorer for performance tuning by brundolf on Saturday May 13, 2023 @11:39AM (#35929423)
They don't keep parity. As far as I know, the official TypeScript implementation is the only major one that performs checking. There are tons of other options for stripping types that are much faster than it, but that's a much easier task.

VSCode at least uses the official checker under the hood; I believe Deno does to, and I would expect IDEA to use it too