Many libraries and/or frameworks come from companies you could argue cannot be trusted (Meta, Google...) but do you shy away from anything they produce and stick to something developed independently somehow? In the case of .Net: it has been around for a long time, and it has changed drastically. It was closed source, Windows-only and it wasn't sleek. Then they rebooted the whole thing into .Net Core. Open source, platform independent, much thinner, development in the open.
> Some people claim .NET developer ergonomics on Linux are fine now, but those I know personally that tells me this are using VSCode, which I consider a rather shoddy piece of software.
My personal experiences with VSCode and the recent C# extensions have been fine for small projects, but if that's not your thing, there's also JetBrains' Rider, which I have very good experiences with as well.
> Maven is a turd, but a very solid one when you've figured out the XML incantation you need. I'm not sure what the alternatives are in .NET-land, or whether I can feel that I trust that they will work fine in ten years, like fifteen year old Maven projects tend to do.
The package manager aspect is Nuget in the .Net ecosystem. It's easier than Maven in the sense that you can control it from your IDE or from the command line, instead of having to edit your pom.xml or the .Net equivalent (which has one extra layer when compared to Maven; solutions containing projects).
> Java has Wildfly. What's the equivalent in .NET? Running a MICROS~1 Windows Server with IIS? That's not an option. The equivalent in .Net is Kestrel, which is part of ASP.Net, and can run on Linux. It's a little less work to setup than Wildfly (which is not a lot of work either) because it's bundled.
> And so on and so on. It's surely not for everyone but I think Microsoft has taken a great turn with it after the "reset". Is it going to be like this forever? I don't know, but looking at the past, at the direction Microsoft has taken it, I think it's gotten much better.
Of course, I wouldn't advocate rewriting your Java-based softwarescape into .Net (or the other way around) lightly, way too expensive and Java will probably get the job done.