3 ms·
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 im
by rektide 3y ago
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.
- brundolf 3y agoThey 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, but that's a much easier task Deno uses tsc internally, and VSCode at least uses the official typescript language server, which I believe uses tsc internally