Microsoft's recent decision to rewrite its TypeScript tool chain using Go has sparked a heated debate among developers, with some questioning why the company chose Go over its own C# or even TypeScript itself. This move has reignited the age-old discussion about the importance of language choice and the so-called "language wars" that often ensue.

The debate has taken many in the industry back to the early days of programming, when developers would passionately argue over the merits of different languages. The author of the article, a veteran developer, recalls his own experiences with BASIC, Pascal, and Delphi, and how these language wars would often get personal and ugly. He notes that the fact that developers had to pay for their development tools in the past may have contributed to their defensiveness about their chosen language.

Today, with most programming languages and basic tools being free, the debate may seem less intense, but it's still prevalent. The author observes that JavaScript, TypeScript, Rust, and C++ developers often find themselves at odds with each other, each convinced that their language of choice is the best. However, he argues that this endless debate is ultimately futile, as there is no one "correct" answer. Instead, developers should focus on choosing the language that works best for them and their project.

The author concedes that there are some obvious wrong answers, such as using GW-BASIC for modern web development, but notes that there are many right answers, with venerable languages like Java, C#, and Python having huge and rich ecosystems. He concludes that the advice to "choose the right tool for the job" may seem trite, but it's ultimately solid advice.

The Microsoft decision to use Go for its TypeScript rewrite has raised eyebrows, but the author argues that if the company believes it's the best tool for the job, then it's not worth arguing about. This episode serves as a reminder that, in the end, the choice of language is just one aspect of the development process, and that there are many ways to build a successful project.

The broader implications of this debate are significant, as it highlights the importance of flexibility and adaptability in the rapidly evolving world of software development. As new languages and frameworks emerge, developers must be willing to consider different options and choose the best tool for the job, rather than getting bogged down in ideological debates about language superiority.

Ultimately, the Microsoft decision to use Go for its TypeScript rewrite serves as a reminder that, in the world of software development, there is no one "right" answer, only a multitude of options that can lead to success. By embracing this diversity and focusing on the task at hand, developers can build better software and move the industry forward.