Maybe now. .NET wasn’t always open, used to be Windows-only, was buggy, version-dependent (but not as bad as the jre could be; true), and had (still has) poor resource-management. I think you’re talking about .NETCore.
That said, I wasn’t commenting on the code viability (I’m not a professional developer) so much as the support overhead required (back when I worked support) for the different versions of .NET, especially when MS stopped including v3.5 in Windows except by using “features and programs” or downloading and installing it manually.
Yeah, that’s pretty dated. There’s one flavor of dotnet (more or less) that runs on everything, and it’s about as efficient as anything with a garbage collector can be.
There are hairs that could be split in there, such as the release cadence, hosting bundle vs desktop runtime, but that’s all much simpler than it used to be. You generally know if you want to run a desktop app vs a webserver.
Maybe now. .NET wasn’t always open, used to be Windows-only, was buggy, version-dependent (but not as bad as the jre could be; true), and had (still has) poor resource-management. I think you’re talking about .NETCore.
That said, I wasn’t commenting on the code viability (I’m not a professional developer) so much as the support overhead required (back when I worked support) for the different versions of .NET, especially when MS stopped including v3.5 in Windows except by using “features and programs” or downloading and installing it manually.
Yeah, that’s pretty dated. There’s one flavor of dotnet (more or less) that runs on everything, and it’s about as efficient as anything with a garbage collector can be.
There are hairs that could be split in there, such as the release cadence, hosting bundle vs desktop runtime, but that’s all much simpler than it used to be. You generally know if you want to run a desktop app vs a webserver.