Loading video...
Video Failed to Load
Microsoft is porting the TS compiler to Go for a massive native speedup – amazing! But why not Rust / C# / etc? Here's Anders Hejlsberg explanation from his Wes Bos interview:
583,757 views • 1 year ago •via X (Twitter)
8 Comments

More details on the decision to port to Go: Michigan TS discussion w/ Anders Hejlsberg: GitHub discussion: Seems to make a lot of sense to me, aside from WASM being less interoperable w/ Go... thoughts?

⌨️ 2AM debugging session: Your code won't compile, Stack Overflow is your best friend, and your Kaiser 4 is the only one who understands... Every developer's late-night reality: 💻 "One more bug fix" turned into sunrise ☕ Coffee cup collection growing 🐛 That bug that just won't die Kaiser 4 speaks fluent Python: 🌟 4D lumbar support for those debugging postures ✨ Perfect height for multiple monitors 💫 Recline mode for code compilation breaks Because good code comes from comfortable devs! ⚡️ Debug in comfort: #AndaSeat #DevLife #CodingLife #ProgrammerSetup #gaming #gamingchair

@ahejlsberg @wesbos Sounds like a skill issue for me.

@ahejlsberg @wesbos Full interview here. Typescript Just Got 10x Faster

@ahejlsberg @wesbos @grok summarize this video

@ahejlsberg @wesbos It was the natural direction for them to "Go".

@ahejlsberg @wesbos literally had a convo about RustScript (hypothetical) yesterday

@ahejlsberg @wesbos I would have preferred swift over Go. Go is this midage cult who resist changes.


