Why TypeScript 7.0 Was Rewritten in Go

Misleading article. Probably partially AI written? Presents nonsense such as eg. the diamond inheritance example as valid-seeming argumentation.

Quite a few points are plain wrong and outdated and under-researched, eg. Python has uv, ruff and Pyrefly, and with that combination, has roughly the same agent ergonomics as Go and lower token count due to higher abstraction level.

It's written in Go because they didn't realize it was a dead-end choice. They optimized their own perf reviews instead of the actual long-term health of the ecosystem...