Post

JauntyWunderKind
@jauntywunderkind.bsky.social

Yeah, I can see that. Bad phrasing on my part. There's no sense waiting. I do wish an actually modular component-model was production ready & widely used, such that a more polyglot & modular future could be taking root here. But, again, no sense waiting for that.

Geoff Goodman
@goodman.dev

What does this mean for use-cases that run in browser-like environments where we can't run native binaries? Will a WASM build and wrapper be created?

Rasmus Schultz
@mindplay.dk

will the Go version replace the TS version of the compiler, or will you be maintaining both? what happens to the considerable ecosystem of compiler extensions that rely on the unofficial APIs? will Node bindings to the Go version provide the same extension points?

Can
@canstand.bsky.social

Why go? bsky.app/profile/fili...

Filippo Valsorda@filippo.abyssdomain.expert

TypeScript team: rewrites compiler in Go. Go community: what do you mean your new compiler takes more than a minute to compile? Unacceptable. Dishonorable even. We are so sorry for this sub par experience. Not how we do things around here. Two days later: WIP 5x speedup. HN: why pick Go anyway?

github.comcmd/compile: slow escape analysis in large package in the typescript compiler · Issue #72815 · golang/goGo version go version go1.24.1 linux/amd64 Output of go env in your module/workspace: AR='ar' CC='gcc' CGO_CFLAGS='-O2 -g' CGO_CPPFLAGS='' CGO_CXXFLAGS='-O2 -g' CGO_ENABLED='1' CGO_FFLAGS='-O2 -g' ...
Martin
@chaosmonster.bsky.social

The thread splits into two sections to me 1. why the educated decision to use go? I thought we collectively decided to rewrite the web in Rust 2. will Doom run and how is the framerate I am team 2, because let’s be honest we are not all reading the typescript checker code at all