I mean you're not wrong... I have someone replying to me on an issue I recently filed with bogus pointers on how to "fix" it on my side (you can't, it's feedback on product behavior). I can't tell if they're a well-intentioned high schooler or just writing AI responses.

This basically signals to me "I don't have a lot of time and I'm not an expert here, but feel free to close if I'm way off and the problem is too involved".

This is actually way better than some drive-by PRs we'd see before AI generated PRs. Easier to manage for us if you're open about that.

While I think you're in part right, I would guess this person isn't trying to be a regular contributor - and knowing that is actually pretty helpful for maintainers!

It's likely that we may need to push out API work to 7.1 or 7.2. We want to have things ready early next year for the core compiler & LS, but the API will be a lot of work on top. We're hoping 6.0 can bridge the tooling gap and we can work with tool authors to prioritize work on 7.x's API.

Fun fact: cute dog GIFs are a prerequisite for any standards work

Putting directly on Object means you can reliably access it without worrying about overrides, null prototypes, or "polluting" every object with new members.

Otherwise, being resilient to overrides means you always have to go through Object.prototype and invoke it in a weird way with call/apply.

So brave.

We're hoping for TypeScript 6.0 early 2026 (think February or earlier) and 7.0 shortly after.

We're looking for people to use the native previews of 7.0 for feedback ASAP though. We feel the language service is pretty solid these days!

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.