Read the discussion on HN. A full-thread summary is not available yet.
dotnet
runtime
C#2019–2026
dotnet / runtime
runtime
.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
197Distinct people
337Mentions
1Explicit recommenders
18.4KGitHub stars
What to know before exploring
What it is
.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
GitHub
Where it is used
- Stack Overflow — Stack Overflow moved their service to .NET Core and saw lower page render times and improved latency. This reflects the site running on the .NET runtime after the migration. Source
What people are saying
> It is irrelevant that the benchmark is written in Oberon. It is not irrelevant from my perspective. It might be mostly irrelevant if Oberon, as you say, "fairly directly"…
rndgermandude used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- dotnet/aspnetcore · linked in 5 of the same discussions
- webassembly/gc · linked in 5 of the same discussions
- dotnet/runtimelab · linked in 4 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:45:45 PM UTC.
Mentions over time
HN mentions by year337 dated mentions
Observed mentions: 2019-12-06 14:10:04 UTC to 2026-09-21 15:39:47 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 26 | 5 | 21 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 34 | 6 | 28 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 51 | 3 | 48 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 38 | 3 | 35 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 96 | 4 | 92 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 79 | 9 | 70 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 12 | 1 | 11 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
.NET Runtime
What is .NET?
How can I contribute?
Reporting security issues and security bugs
Filing issues
Useful Links
.NET Foundation
License
This repo contains the code to build the .NET runtime, libraries and shared host (dotnet) installers for
all supported platforms, as well as the sources to .NET runtime and libraries.
What is .NET?
Official Starting Page: https://dotnet.microsoft.com
How to use .NET (with VS, VS Code, command-line CLI)
Install official releases
Documentation (Get Started, Tutorials, Porting from .NET Framework, API reference, ...)
Deploying apps
Support (Releases, OS Versions, ...)
Roadmap
How can I contribute?
We welcome contributions! Many people all over the world have helped make this project better.
Contributing explains what kinds of contributions we welcome
Workflow Instructions explains how to build and test
Dogfooding .NET explains how to get nightly builds of the runtime and its libraries to test them in your own projects.
Reporting security issues and security bugs
Security issues and bugs should be reported privately to the Microsoft Security Response Center (MSRC) via the MSRC Researcher Portal. You should receive a response within 24 hours. Further information can be found in the Security TechCenter. You can also find these instructions in this repo's Security doc.
Also see info about related Microsoft .NET Bounty Program.
Filing issues
This repo should contain issues that are tied to the runtime, the class libraries and frameworks, the installation of the dotnet binary (sometimes known as the muxer) and the installation of the .NET runtime and libraries.
For other issues, please file them to their appropriate sibling repos. We have links to many of them on our new issue page.
Useful Links
.NET source index / .NET Framework source index
API Reference docs
.NET API Catalog (incl. APIs from daily builds and API usage info)
API docs writing guidelines - useful when writing /// comments
.NET Discord Server - a place to discuss the development of .NET and its ecosystem
.NET Foundation
.NET Runtime is a .NET Foundation project.
There are many .NET related projects on GitHub.
.NET home repo - links to 100s of .NET projects, from Microsoft and the community.
ASP.NET Core home - the best place to start learning about ASP.NET Core.
This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behavior in our community. For more information, see the .NET Foundation Code of Conduct.
General .NET OSS discussions: .NET Foundation Discussions
License
.NET (including the runtime repo) is licensed under the MIT license.
Read the full README on GitHubWhat Hacker News says
51 sources> I've seen people writing C# applications and wondering why stuff is taking 200ms
I observe that in the most recent generation of its HTTP client (SocketsHttpHandler), .NET also sets NoDelay by default.
https://github.com/dotnet/runtime/blob/main/src/libraries/Sy...
In Golang disables Nagle's Algorithm by defaultDoes .NET 6 support windows 98
2 points · Open discussionFeel free to open an issue for this over at github.com/dotnet/runtime, if you have code you can share.
In .NET 7 is Available TodaySpot on, this was the original intent of the linked implementation but the PR eventually did not progress and got rejected[0].
However, it might not be off the table yet, because scaling per core is dramatically better especially in moderate to write-heavy scenarios which remains the main use case for ConcurrentDictionary. I have been benchmarking it on arm64 lately and it shows different numbers much more favoring non-blocking implementation without any regressions discussed in the PR.
[0] https://github.com/dotnet/runtime/pull/50337
In LiteDB: A .NET embedded NoSQL databaseThere’s one of those for C++ too, say hello to the .NET garbage collector: https://github.com/dotnet/runtime/blob/main/src/coreclr/gc/g...
In CS quotes found while browsing Notepad++'s codeWell, .NET's garbage collector certainly springs to mind. Not exactly in a good way. You know you have something special on your hands when GitHub refuses to show you a highlighted version of a hand written C++ file (https://github.com/dotnet/runtime/blob/98984ccad55362a66b7fd...).
Other than that, I remember my mind was blown a few times while watching Jim Weirich's presentation on functional programming all those years ago (https://www.youtube.com/watch?v=FITJMJjASUs).
In Ask HN: What piece of code/codebase blew your mind when you saw it?It's a good point, after so long why the JVM is not written in Java actually?
For example the Go runtime and I think C# as well are written in their respective language.
https://github.com/golang/go/tree/master/src/runtime
https://github.com/dotnet/runtime
In Oracle Contributing GraalVM Community Edition Java Code to OpenJDKReferenceSource is the code from the Windows framework and I'm pretty sure it should be considered deprecated at this point. The runtime and core libraries are now at https://github.com/dotnet/runtime, kinda weird that this is not directly linked in the home page repo.
In Ask HN: Examples of Top C# Code?UnreachableException has no special behaviour at all [0]. It's just a standardized 'tag' around regular Exception.
The only advantage of using a standard tag is that it will be recognized by other programmers, and maybe some supporting tooling might choose to give it special treatment.
E.g. a code analyzer could warn you if you raise a NotImplementedException (forgot to finish a feature?), but accept an UnreachableException as valid.
If you want to add a custom name (for easier grepping maybe?) or stuff some extra data in the exception, you can still inherit from UnreachableException.
[0] https://github.com/dotnet/runtime/pull/63922/files#diff-588c...
In That Shouldn't Happen – UnreachableException in .NET 7If I understand this API correctly, Java won't get a distinct float16 type. It seems that they'll have 16 bit floats encoded in shorts (16 bit integers).
This seems like it could be a huge footgun. A lot of methods already have an overload for short, so a completely separate set of functions are needed to do operations on them.
I get that it's hard to introduce a 16 bit float as a new primitive type in the JVM, so that's most likely not an option.
.NET introduced 16 bit floats as the "Half" type 2 years ago [1] and I think their approach is far superior. They're also saving it as a (u)short internally [2], but they have something that Java (still?) does not have: They made it a user-defined value type, or when using C# language: a struct.
This doesn't create footguns because it is a separate type and also doesn't have any meaningful overh
Read the rest
ead. And since .NET 7 will introduce generic math [3], we'll seem to be able to use the same APIs as we've always done.
IMHO, this is an API - just like Optional<T> - which could be far better designed if project valhalla would already be a thing.
[1]: https://devblogs.microsoft.com/dotnet/introducing-the-half-t...
[2]: https://github.com/dotnet/runtime/blob/d783badaa38596beedefd...
[3]: https://devblogs.microsoft.com/dotnet/dotnet-7-generic-math/
Unfortunately looks like still no compact strings like Java or JS:
https://github.com/dotnet/runtime/issues/6612
You can work around it, but it's nice in languages where common text doesn't take double the memory (because of utf8 or compact strings).
In Performance Improvements in .NET 7“As a client, not being able to make encrypted connections to TLS 1.3-only services/servers is by far the bigger issue.”
https://github.com/dotnet/runtime/issues/1979
In Ask HN: Is doing .NET development on a Mac viable today?Microsoft publishes a patent promise here, though: https://github.com/dotnet/runtime/blob/main/PATENTS.TXT
In .NET 6 is now in Ubuntu 22.04For FreeBSD support, see the following issue for the porting effort. The community has been working like hell to make it happen since 2015 and at this point we have regular unofficial builds:
https://github.com/dotnet/runtime/issues/14537
About 2 months ago they crushed hopes that official FreeBSD support will happen anytime soon by clearly stating that at this point, updating their Quality Assurance process to support FreeBSD would not make business sense for them as they have to put together an extensive test suit and manual testing procedures for every OS. Microsoft folks remain friendly and helpful in the thread though.
The FreeBSD ports system insists on requiring third party applications to be able to be built from source offline, while the .NET build process downloads packages left and right at various parts of the process. This i
Read the rest
s one of the things that complicates its inclusion in the ports tree. Building .NET for FreeBSD is close to rocket science, the community has worked to make the process way simpler. It is frustrating that the .NET team refuses to take things from there. Providing FreeBSD support is what I would expect from them to strengthen their cross-platform posture. This is the last major platform they need to support, and one being heavily used for servers.
Folks are working on FreeBSD support: https://github.com/dotnet/runtime/pull/71486
In .NET 6 is now in Ubuntu 22.04Showing the 15 most recent of 51 sources. Enable JavaScript to search and browse every indexed mention.