+1 for simple. Something you don’t need to host.

And DPI relies on endpoints using their CA and MiTM certificate. It’s not like it can happen without your knowledge (at least on personal devices). After implementing DPI on multiple different firewall devices on home and enterprise networks, it’s a fairly deliberate setup process on the endpoint. Not a, “they can listen in whenever they want,” scenario.

But fuck this bot 🤖

That’s not Linux, though; that’s docker.

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.

Many of us started running Windows Server and endpoints, but in my case, the cost and substandard tools turned me away. I was running A DLNA server and using WDS (yes, very overkill for home, but fun to learn for work), but then I found TrueNAS (then called FreeNAS) running on BSD. I now run a simple share from there and Kodi on my (Linux and Android) user endpoints. I don’t bother with imaging anymore, and use dd for backups to my NAS. My Firewall runs OPNSense (BSD) and I run OpenWRT on two TrendNet WAPs.

I’ll never go back to MS. It’s just not a welcoming platform from my perspective. Don’t even get me started on .NET or the various and sundry “redistributables” constantly required by every tool you try to use.

my distaste for MS grew

This is a natural progression. Inescapable.