TS Go Port and Slow Types

[KnorpelSenf]

https://devblogs.microsoft.com/typescript/typescript-native-port/ is a thing now and TS gets 10X faster. This poses two questions:

1. Is it still reasonable to argue that calling into tsc is slow (something that was very obvious with the JS version of tsc)?
2. What does this mean for slow types?

[AugustinMauroy]

The question shouldn't be throw now because this "new" project isn't published

[KnorpelSenf]

It's published and starting to be usable for some tasks already, and it is definitely going to be very much inevitable for any serious project building on top of TS. JSR is such a project, so it makes sense to discuss this. Just because they didn't configure a build step in CI yet, doesn't mean it's not relevant.

[AugustinMauroy]

Oh wow interesting. I wasn't aware of that. for moment type checking with JSR cli/deno is done by tsc cli under the hood. So wee need to see what deno will do.

[lishaduck]

I'd guess that slow types will remain. For large projects, even a 10× speedup might not be enough, and the issue of types becoming unstable over time will remain (although JSR could potentially cache the output).

[typed-sigterm]

I still think #15 is better 🤔

[KnorpelSenf]

I actually agree that faster tsc means faster checks but nothing beyond that. My personal take is that TS 7.0 does not change anything about the fact that we should encourage developers to use isolatedDeclarations. I guess slow types are a way to move people towards better code, and this aspiration does not change because some tool gets faster.

[KnorpelSenf]

Seems like nobody has anything to add. Closing.