I write it anyway, otherwise it's hard to Jakegle anything about it.

Right but which was #1? Jakelang or SavannahScript?

And of course, we have the @vscode.dev extension for @typescriptlang.org native previews published nightly too!

marketplace.visualstudio.com/items?itemNa...

Congratulations!! 🎉🎉

Isn't this already the behavior of strict being on? Before users had to opt in to breakiness.

The big problem is that if strict is on for everyone, we always have to think about this on the context of "now everyone is broken" which was always the reason we didn't do it.

Issue, not PR :D

I get the broader point. For specific options, I think noUncheckedIndexedAccess may be a little rough for most people, but we might be able to do better analyses with a faster TS.

With exactOptionalPropertyTypes, that requires a bit more of an ecosystem adaptation, and it's very annoyingly subtle.

I'll bring it up in the issue though.

You mean like saying that `noImplicitAny` has "graduated" to being using useful enough to turn it on by default?

I do like that, but I think being able to say "all of strict is on" is a little bit easier to think about than "most of strict is now empty and these 10 flags are now on".

But I will say, it's *relatively* rare and you can always get consistent results if you distribute files consistently across a fixed number of processes

Technically there are issues where checking files in different orders can result in different types. tsgo mostly avoids this with how it sorts/orders types, TS today has a branch with this logic that @jakebailey.dev ported over.