ASP.NET Core VS .NET Runtime

Compare ASP.NET Core vs .NET Runtime and see what are their differences.

ASP.NET Core

ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux. (by dotnet)

.NET Runtime

.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps. (by dotnet)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
ASP.NET Core .NET Runtime
1,632 606
34,312 14,047
1.6% 2.2%
9.9 10.0
2 days ago 7 days ago
C# C#
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

ASP.NET Core

Posts with mentions or reviews of ASP.NET Core. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-09.

.NET Runtime

Posts with mentions or reviews of .NET Runtime. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-22.
  • The Performance Impact of C++'s `final` Keyword
    5 projects | news.ycombinator.com | 22 Apr 2024
    Yes, that is true. I'm not sure about JVM implementation details but the reason the comment says "virtual and interface" calls is to outline the difference. Virtual calls in .NET are sufficiently close[0] to virtual calls in C++. Interface calls, however, are coded differently[1].

    Also you are correct - virtual calls are not terribly expensive, but they encroach on ever limited* CPU resources like indirect jump and load predictors and, as noted in parent comments, block inlining, which is highly undesirable for small and frequently called methods, particularly when they are in a loop.

    * through great effort of our industry to take back whatever performance wins each generation brings with even more abstractions that fail to improve our productivity

    [0] https://github.com/dotnet/coreclr/blob/4895a06c/src/vm/amd64...

    [1] https://github.com/dotnet/runtime/blob/main/docs/design/core... (mind you, the text was initially written 18 ago, wow)

  • Java 23: The New Features Are Officially Announced
    5 projects | news.ycombinator.com | 17 Apr 2024
    If you care about portable SIMD and performance, you may want to save yourself trouble and skip to C# instead, it also has an extensive guide to using it: https://github.com/dotnet/runtime/blob/69110bfdcf5590db1d32c...

    CoreLib and many new libraries are using it heavily to match performance of manually intensified C++ code.

  • Locally test and validate your Renovate configuration files
    4 projects | dev.to | 9 Apr 2024
    DEBUG: packageFiles with updates (repository=local) "config": { "nuget": [ { "deps": [ { "datasource": "nuget", "depType": "nuget", "depName": "Microsoft.Extensions.Hosting", "currentValue": "7.0.0", "updates": [ { "bucket": "non-major", "newVersion": "7.0.1", "newValue": "7.0.1", "releaseTimestamp": "2023-02-14T13:21:52.713Z", "newMajor": 7, "newMinor": 0, "updateType": "patch", "branchName": "renovate/dotnet-monorepo" }, { "bucket": "major", "newVersion": "8.0.0", "newValue": "8.0.0", "releaseTimestamp": "2023-11-14T13:23:17.653Z", "newMajor": 8, "newMinor": 0, "updateType": "major", "branchName": "renovate/major-dotnet-monorepo" } ], "packageName": "Microsoft.Extensions.Hosting", "versioning": "nuget", "warnings": [], "sourceUrl": "https://github.com/dotnet/runtime", "registryUrl": "https://api.nuget.org/v3/index.json", "homepage": "https://dot.net/", "currentVersion": "7.0.0", "isSingleVersion": true, "fixedVersion": "7.0.0" } ], "packageFile": "RenovateDemo.csproj" } ] }
  • Chrome Feature: ZSTD Content-Encoding
    10 projects | news.ycombinator.com | 1 Apr 2024
    https://github.com/dotnet/runtime/issues/59591

    Support zstd Content-Encoding:

  • Writing x86 SIMD using x86inc.asm (2017)
    3 projects | news.ycombinator.com | 26 Mar 2024
  • Why choose async/await over threads?
    11 projects | news.ycombinator.com | 25 Mar 2024
    We might not be that far away already. There is this issue[1] on Github, where Microsoft and the community discuss some significant changes.

    There is still a lot of questions unanswered, but initial tests look promising.

    Ref: https://github.com/dotnet/runtime/issues/94620

  • Redis License Changed
    11 projects | news.ycombinator.com | 20 Mar 2024
    https://github.com/dotnet/dotnet exists for source build that stitches together SDK, Roslyn, runtime and other dependencies. A lot of them can be built and used individually, which is what contributors usually do. For example, you can clone and build https://github.com/dotnet/runtime and use the produced artifacts to execute .NET assemblies or build .NET binaries.
  • Garnet – A new remote cache-store from Microsoft Research
    6 projects | news.ycombinator.com | 18 Mar 2024
    Yeah, it kind of is. There are quite a few of experiments that are conducted to see if they show promise in the prototype form and then are taken further for proper integration if they do.

    Unfortunately, object stack allocation was not one of them even though DOTNET_JitObjectStackAllocation configuration knob exists today, enabling it makes zero impact as it almost never kicks in. By the end of the experiment[0], it was concluded that before investing effort in this kind of feature becomes profitable given how a lot of C# code is written, there are many other lower hanging fruits.

    To contrast this, in continuation to green threads experiment, a runtime handled tasks experiment[1] which moves async state machine handling from IL emitted by Roslyn to special-cased methods and then handling purely in runtime code has been a massive success and is now being worked on to be integrated in one of the future version of .NET (hopefully 10?)

    [0] https://github.com/dotnet/runtime/issues/11192

    [1] https://github.com/dotnet/runtimelab/blob/feature/async2-exp...

  • Common Sorting Algorithms in C# - From My Experience
    1 project | dev.to | 2 Mar 2024
    Orderby Linq Code Reference
  • The Mechanics of Silicon Valley Pump and Dump Schemes
    8 projects | dev.to | 18 Feb 2024
    The math of the above is really simple. Microsoft has 13,000 stars on their GitHub profile for their flagship product. SupaBase has 63,000 stars on their GitHub project for their flagship product. 27% of all software developers in the world are using .Net. SupaBase has 4.5 times as many likes as the .Net Core runtime, so they must be 4.5 times as large, right? 4.5 multiplied by 27% becomes 130%. Implying 130% of all software developers that exists on earth are using SupaBase (apparently!)

What are some alternatives?

When comparing ASP.NET Core and .NET Runtime you can also consider the following projects:

Blazor.WebRTC

Ryujinx - Experimental Nintendo Switch Emulator written in C#

Introducing .NET Multi-platform App UI (MAUI) - .NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.

actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.

deno - A modern runtime for JavaScript and TypeScript.

WASI - WebAssembly System Interface

inertia-laravel - The Laravel adapter for Inertia.js.

CoreCLR - CoreCLR is the runtime for .NET Core. It includes the garbage collector, JIT compiler, primitive data types and low-level classes.

PuppeteerSharp - Headless Chrome .NET API

vgpu_unlock - Unlock vGPU functionality for consumer grade GPUs.

CefSharp - .NET (WPF and Windows Forms) bindings for the Chromium Embedded Framework

runtimelab - This repo is for experimentation and exploring new ideas that may or may not make it into the main dotnet/runtime repo.