> .NET as a back-end but most of the startup or tech focus companies are using open source.
.NET is open source under MIT. Come on. Are you living under a rock or something?
https://github.com/dotnet/coreclr/blob/master/LICENSE.TXT
In Ask HN: How good is the job market for .NET stack?dotnet
coreclr
Languages & Compilers2015–2025
dotnet / coreclr · Archived
coreclr
CoreCLR is the runtime for .NET Core. It includes the garbage collector, JIT compiler, primitive data types and low-level classes.
97Distinct people
137Mentions
2Explicit recommenders
12.8KGitHub stars
What to know before exploring
What it is
CoreCLR is the runtime for .NET Core. It includes the garbage collector, JIT compiler, primitive data types and low-level classes.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
> ... is one of my favorite side effects of it being open sourced. Agree! I would never have the time or expertise to work all this out just using WinDBG or similar. Having the…
matthewwarren used a recommendation phrase. 2 indexed comments match. 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/corefx · linked in 7 of the same discussions
- dotnet/roslyn · linked in 4 of the same discussions
- aspnet/mvc · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:56:55 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year137 dated mentions
Observed mentions: 2015-02-03 18:07:42 UTC to 2025-04-14 18:28:02 UTC.
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 |
|---|---|---|---|---|---|
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 44 | 6 | 38 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 23 | 3 | 20 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 24 | 5 | 19 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 17 | 3 | 14 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 23 | 3 | 20 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 0 | 1 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
Going forward, the .NET team is using https://github.com/dotnet/runtime to
develop the code and issues formerly in this repository.
Please see the following for more context:
dotnet/announcements#119 "Consolidating .NET GitHub repos"
Read the full README on GitHubWhat Hacker News says
24 sourcesAlso says
> The .NET runtime supports a wide variety of high performance applications. As such, performance is a key design element for every change.
https://github.com/dotnet/coreclr/blob/master/Documentation/...
In A Look at the Internals of 'Tiered JIT Compilation' in .NET Core> The Book of the Runtime documentation states "The goal of the CLR is to make programming easy"
In case anyone else is interested, that quote comes from https://github.com/dotnet/coreclr/blob/master/Documentation/...
In A Look at the Internals of 'Tiered JIT Compilation' in .NET CoreUnsafe is no longer necessary for such cases. This can now be written as:
Span<byte> stackSpan = stackalloc byte[100];
See https://github.com/dotnet/coreclr/pull/14503/files as an example.
In Span in C#As long as we have things like this: https://github.com/dotnet/corefx/issues/19773
And this: https://stackoverflow.com/questions/27266907/no-appdomains-i...
And did I mention this? https://github.com/dotnet/coreclr/pull/8677
As long as we have things like that, and as long as .NET Core continues to pander only to the lowest common denominator of developers, then the Mono project is still providing value. It is not a matter of "competing".
In Mono's New .NET InterpreterHmm, that's a really good question.
I did a quick search in AppDomain.cpp [0] for 'generic' and there's quite a few comments/variables that mention it. Maybe this [1] is one of the tricky interactions?
[0]: https://github.com/dotnet/coreclr/blob/master/src/vm/appdoma...
[1]: https://github.com/dotnet/coreclr/blob/master/src/vm/appdoma...
In A DoS Attack Against the C# Compiler> neither free nor very open.
.NET is released under MIT license[0]. What the hell are you talking about.
[0] https://github.com/dotnet/coreclr/blob/master/LICENSE.TXT
In StackOverflow Architecture (2016)In-Depth Tutorial on RyuJIT (the .NET Core JIT)
2 points · Open discussionI don't know what's taking up the memory in those benchmarks.
However in CoreCLR there are multiple efforts to reduce memory consumption, mostly driven by the ports to other architectures (e.g. ARM, ARM32), see https://github.com/dotnet/coreclr/search?q=memory+consumptio...
In Performance Improvements in .NET CoreIf you take a look as these issues, it's clear that they're happy to make the source code very different, i.e. hard/impossible for changes to be automatically ported across.
Just look at how much .NET Framework (Desktop) code they removed from CoreCLR earlier this year!
- https://github.com/dotnet/coreclr/issues/8857
- https://github.com/dotnet/coreclr/issues/8763
- https://github.com/dotnet/coreclr/issues/4651
- https://github.com/dotnet/coreclr/pull/9058
In Performance Improvements in .NET Core> I still haven't quite grasped the relation between core and the full framework when it comes to fixes like this being merged into the full framework.
From what I can tell, from following the CoreCLR repo (https://github.com/dotnet/coreclr), it's changed over time.
In the beginning the sources of the 2 were more closely tied, changes were (automatically?) copied over. Now it seems like it's more ad-hoc, done as and when they decide it's needed. See the mentions of 'TFS Mirror' in this thread for a bit more info https://github.com/dotnet/coreclr/issues/972#issuecomment-25...
In Performance Improvements in .NET Core> One might argue that replacing 3d party libraries isn't doing the "core parts" better, it's just being bloated.
First, they're not "replacing" anything. Printing, image acquisition, font rendering, advanced tracing (ETW), authentication and directory (Kerberos), remote access, internationalization, etc. are core OS services. Second, I recently installed Win10 on a machine intended for embedded use. All this "bloat" took ~10GB of disk space, compared to the most plain, cheapest OVH installation which used 2.5GB of disk space and doesn't deliver nearly 1/4 of the features that Windows does.
So which "bloat" are we talking about?
> Moreover, it's being bloated without choice because most people just use the included version so alternatives don't get to thrive.
If the OS-provided version is well thought-out [1] (APIs since Vista seem to be)
Read the rest
, why would I want an "alternative" that, even if it provides exactly the same functionality, isn't integrated with the rest of the system? (Thankfully, systemd is attacking the integration aspect.) Linux is full of "almost does the job" alternatives, as exemplified in [2]. Thank you, but I'll choose the OS-provided facility, not the least because it vastly simplifies deployment.
[1] EDIT: "Well though-out" is not the same as "easy to use". My impression is that C-level APIs are designed for performance and flexibility first, ease of use comes second.
[2] https://github.com/dotnet/coreclr/blob/master/Documentation/...
COMPlus_JitDisasm lead me to this [1]. Thanks!
[1] https://github.com/dotnet/coreclr/blob/master/Documentation/...
In Adding a new Bytecode instruction to the .NET runtimeShowing the 15 most recent of 24 sources. Enable JavaScript to search and browse every indexed mention.