It seems that you might be asking this question in bad faith.

But on the off chance you are not, please find previous replies that address the same kind of question below:

https://news.ycombinator.com/item?id=41037792

https://news.ycombinator.com/item?id=41189309

https://news.ycombinator.com/item?id=41211767

https://news.ycombinator.com/item?id=41197493

https://news.ycombinator.com/item?id=41218353

I understand its probably not the case today, just that C# shares some of the MS reputation and its hard to get rid of. Especially when there are dozens of open-source independent languages around.

I think phrasing with insistence that it is "probably not the case today" despite demonstrable evidence of certainty means that your motivation for this reply was not to learn something new or share something you know but to try to get a raise with low-effort bait. This is both tiresome and goes against guidelines.

Somehow we all can normally discuss programming languages without bringing practices of Google or Oracle into the picture and focus instead on programming language development initiatives that they drive and sponsor, that are themselves sufficiently independent. Let's keep it that way.

Also https://news.ycombinator.com/item?id=41218353 (which was the last link in the list).

I phrase it this way only because I do not have enough knowledge to be certain. I've read the comments that you sent, but to be certain it requires much more in-depth investigation which I don't want to do simply because I have no plans on interacting with C# in any forceable future.

I only tried to explain how some people who are not directly involved with C# might see the language.

That's a shame. .NET does away with all the pain points you've grown to expect from Python or Java tooling, has arguably better support[0] story on the main platforms nowadays and extremely no-nonsense CLI tooling similar to Rust or Go:

    sudo dnf/apt install dotnet-sdk-8.0
    # or
    brew install dotnet-sdk

    dotnet new web
    dotnet run
    curl localhost:5050

[0]: Situations like https://blogs.oracle.com/java/post/java-on-macos-14-4 do not happen to .NET as it tries to use the platforms it is targeted at in a "canonical way". To be fair, not exactly a Java fault, but effort is invested to ensure that the runtime plays nicely with e.g. memory protection techniques.

This is no longer remotely true. Most .NET teams I know now deploy on Linux and develop on Windows/Mac/Linux.