Content pfp
Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions

Kevin pfp
Kevin
@typedarray.eth
The TypeScript team is rewriting the compiler in Go. Incredible news. https://x.com/typescript/status/1899469817863888958
5 replies
6 recasts
39 reactions

christopher pfp
christopher
@christopher
Why pick Golang when SWC has already done most of the heavy lifting?
4 replies
1 recast
3 reactions

christopher pfp
christopher
@christopher
Ah they're worried about unsafe code and delays. But.. we have AI for this grunt work and backchecking? Perplexing. https://www.reddit.com/r/javascript/comments/1j8s441/comment/mh7ms9n/
1 reply
0 recast
1 reaction

Kevin pfp
Kevin
@typedarray.eth
It sounds like they are doing more of a "find and replace" style rewrite rather than a from-scratch rewrite. Data structures and algorithms not really changing, etc. Which is quite interesting - my mental model is that usually the main benefit a rewrite is the chance to revisit the core DS/A decisions.
3 replies
0 recast
2 reactions

christopher pfp
christopher
@christopher
Very Microsoft of them to not dig deep and scratch it lol.
1 reply
0 recast
2 reactions

Rafi pfp
Rafi
@rafi
TypeScript typing system is full of JS idiosyncrasy and it branches off from some mandates found in programming type theory that is common in other widely implemented type systems. There are few people in the world who comprehend it and most of them probably work on TypeScript. Having that in mind, make sense they will keep the core intact as all the tactile knowledge gained over the years of few individuals would go to waste.
0 reply
0 recast
1 reaction

Korede pfp
Korede
@korede
From the explanatory video, it seems they consider it more a “port” than a rewrite. Probably speeds up the process and makes it easier to convert the existing tests.
0 reply
0 recast
1 reaction