Deno 2.6
deno.com> We’ve seen 2x speed improvements in type checking times for internal projects when using TSGO.
That's a lot less that what TSGO promised when it was first announced (A 10x faster Typescript¹). Hopefully this is just the result of it being experimental.
1: https://devblogs.microsoft.com/typescript/typescript-native-...
The article is measuring full project build performance. That includes type-checking and compilation.
Maybe the `tsc` type-checker was already fast (so we only get some speed improvements in `tsgo`), or the `tsc` compiler was not that fast (so we get a lot of speed improvements in `tsgo`)?
*Update:* There was a performance regression in incremental type-checking between `tsgo` preview 20251209 and 20251211 [1]. But `deno` is using `tsgo` 0.1.11 which was already released last week (before this regression). So, does not seem to influence the type-checking times here.
[1] https://github.com/microsoft/typescript-go/issues/2341 [2] https://github.com/denoland/deno/blob/v2.6.0/cli/tsc/go/tsgo...
You should look into the latest posts on the subject.
> Just as a reminder, even without --incremental, TypeScript 7 often sees close to a 10x speedup over the 6.0 compiler on full builds!
https://devblogs.microsoft.com/typescript/progress-on-typesc...
> dx defaults to --allow-all
And just like that, there goes 50% of it's reason to exist
Has Deno caught up to Bun yet?
On what aspect?