MAmananaysiempre·May 3, 2023
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 those down on a whim.
Does anyone know where the open xlang implementation of MIDL[3] went, 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[4].)
[1] https://dusted.codes/can-we-trust-microsoft-with-open-source and links there
[2] https://g
Read the rest
ithub.com/microsoft/pylance-release/issues/4
[3] https://github.com/microsoft/xlang/pull/529
[4] I vaguely remember a GitHub issue where a Microsoft employee explicitly refused to provide one ("not a priority" or some such synonym for "we don't care, fuck off"), but I can't find it