this post was submitted on 14 Jun 2026
107 points (86.4% liked)
Selfhosted
59939 readers
300 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.