Microsoft chose Go instead of C# or Rust to rewrite TypeScript

[Brother Bill]

On Monday, 8 September 2025 at 20:10:52 UTC, Sergey wrote:
> On Monday, 8 September 2025 at 19:55:20 UTC, Neto wrote:
>>
>> Why isn't D production ready?

One has to ask why to choose a production language.

1. First one has to be aware that it exists.
    a. See Eiffel and D
    Eiffel has been in production since 1985.
    If you use the native version, it works as advertised.
    Eiffel has had great challenges playing nice with .NET, not 
quite there.

2. Management needs to know someone who is already using D/Eiffel.
    If the sphere of influence such as staff, related businesses, 
other management,
    recruiters haven't heard of D/Eiffel, that can be the end of 
the discussion.

3. Management needs to run a small demo project that solves a 
problem they have.

4. There needs to be a way to quickly spin up / train D 
developers, who already know C, C++, Java
    and C#.

5. There needs to be a BIG PAYOFF in one or more of the following 
areas:
    a. Cost, such as AWS servers.
    b. Cost as in writing new functionality.
    c. Cost as in maintaining existing code.
    d. Ease of adding in new features.
    e. Likelihood of code released to production JUST WORKS.
    f. Ease of finding D developers
       If they put out a request for 3 D developers, and they get 
100 resumes,
       that will put their mind at ease that there are D 
developers out there.
    g. Quality of code, so that customers aren't performing QA 
duties.
       If code is error prone, and customers notice it, they are 
less likely to renew
       their contracts.  They are also known to spread the word 
that Company X is slop job.

IMHO, if the development team uses D, OOP using Design by 
Contract (DbC), unit tests,
code review, volume testing, etc., the code written in D should 
be Production Ready.