C# devs are having a meltdown… over Go?
The TypeScript team is rewriting the compiler… in Go.
C# devs expected C#, but Microsoft said nope.
Now, the internet is on fire.
I get it—C# is powerful, battle-tested, and, well… Microsoft’s own baby. Yet, they still chose Go.
Sure, it stings if you’re a C# dev. But let’s be honest—was Go actually the right choice? Or is this just another classic tech outrage?
I gave Go a shot for a week—here’s why it won:
✅ Native binary support – C#’s Native AOT isn’t fully there yet. A compiler needs to run everywhere, and Go delivers.
✅ Simplicity – Go is like C’s clean evolution, while C# leans towards C++ and Java. Porting TS to Go syntax is just easier.
✅ Data structures – Go treats data and logic separately, whereas C# mixes them using OOP. The TS compiler’s structures already resemble Go’s syntax, making porting much smoother.
What do you think—valid outrage or overreaction? 🔥
