Codebase    | TypeScript 6 | TypeScript 7 | Speedup
    ------------|--------------|--------------|--------
    vscode      | 125.7s       | 10.6s        | 11.9x
    sentry      | 139.8s       | 15.7s        | 8.9x
    bluesky     | 24.3s        | 2.8s         | 8.7x
    playwright  | 12.8s        | 1.47s        | 8.7x
    tldraw      | 11.2s        | 1.46s        | 7.7x

Quick question: How does this affect downstream tools like tsdown and esbuild, which need to build the TypeScript codebase? Can I use TS 7 and current tsdown together?

I love TypeScript, if nothing else for how it's been able to popularize types.

huge congrats to the team!

looking forward to the Rust rewrite ;)

Microsoft: Take that, Joel!

;)

---

[1] https://www.joelonsoftware.com/2000/04/06/things-you-should-...

¹https://github.com/Nsttt/typescript-go

My project is a webapp, but I have node types in my ide tooling because of vite.config.ts, and playwright and unit tests. If I add a node api to a react component, tsc won't complain.

Current method to isolate dom lib from node lib requires project reference spaghetti, numerous tsconfig.json and tsbuildinfo output files, and avoiding emitting types with project references is cumbersome.

It always surprises me how little complaints there have been on HN about tsc's performance. I do both TypeScript and Rust at work, and I've seen orders of magnitude more comments on the web about how “rustc is slow” than complaints about tsc's performance and it never stops to surprise me given than in practice the later have annoyed me consistently more than the former.

Even for front end code destined for the browser I rely on Node's type stripping.

I have a longer blog post or audio to post. but in short - the javascript/typescript ecosystem is like working with wood.

you can have your cheap, laminate cardboard wood - Ikea type - the code equivalent will be vibe coded apps that are not original.

then on the high end - you can have your crafted furniture | wooden skyscrapers - that use custom joinery & lamination techniques using young lumber to make to make beams that are fireproof. you can also have high end stuff in the javascript/typescript ecosystem that uses A.I as one uses powerful machine tools but with crafting in mind.

for those that dare to make or dare to do - embrace the typescript|javascript ecosystem.

I've been thinking about this since 2022 and haven't really gotten further than "Hmm, I would like this".

I'm aware that tooling catches most stuff, but being able to shift this even more to the left (compile time) would be great.

I'm just very used to Rust, where my hand is being held

So I'm interested on what exactly has been sped up here. I can see compile times have been, but is that it? I suppose the runtime itself was always native code, and already very fast.

Over the past year, I've been working on porting the v7 tsgo compiler back into TypeScript - https://github.com/tsoniclang/tsts

It's fully functional now, but 2x slower than the original tsc and 10x slower than tsgo. But hopefully in a month or so, we'll get to C# and Rust targets and it should be able to compile itself to become nearly as fast as tsgo.

thanks DanRosenwasser and team for building such an awesome tool for so many years!

I am still of the opinion that well organized and named JS is all that anyone needs and typescript only exists for fresh graduates and fleeing OOP devs.

edit: also the downvote button HN is not for disagreeing with comments or unpopular opinions.

A clean django project is probably 3-4x less code than the equivalent TS based service.

It made me consider dropping strict mode and defaulting to js for most simple things.