I didn't pick .NET, parent did. And regardless if the ecosystem is nice to work in or not, Microsoft tries their true and tested strategy of EEE with that ecosystem as well.

The example is not .NET in general, but that specific event when Microsoft reneged on open development tooling[1]. For some people, that was the moment they stopped trusting "new Microsoft" to keep their word (though for me, it was when the Python language server was replaced with a DRM-locked, LSP-noncompliant one[2] a bit before that; unlike with .NET hot reload, they didn't backtrack there). I can think the company makes great open .NET tools and at the same time not trust them to close it down on a whim.

Does anyone know where the open xlang implementation of MIDL went[3], by the way? (Unlike the original 1990s MIDL, you can't reimplement this one from the language grammar in the docs, because there is no language grammar in the docs.)

[1] https://dusted.codes/can-we-trust-microsoft-with-open-source and links there

[2] https://github.com/microsoft/pylance-release/issues/4

[3] https://github.com/microsoft/xlang/pull/529

> since .NET ecosystem is one of the most sanest out of all ecosystems

Is it? This is the same ecosystem that has .Net, .Net Core, .Net Standard, and .Net Framework as all different (and overlapping? who knows) products?

Its only .Net now.

The Core and Standard things was just there the aid the transition from Framework, which is now complete, any remains will soon be phased out entirely.