announcements
.NET Runtime
announcements | .NET Runtime | |
---|---|---|
16 | 611 | |
1,231 | 14,177 | |
0.0% | 1.9% | |
0.0 | 10.0 | |
almost 2 years ago | 3 days ago | |
C# | ||
Creative Commons Attribution 4.0 | MIT License |
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.
announcements
- BinaryFormatter is being removed in .NET 9
- Announcing the .NET Virtual Monolithic Repository · dotnet/announcements
- .NET Announcing a Monorepo
- .NET's Monorepo
-
Vulnerability found affecting System.Data.SqlClient in Microsoft .Net (Framework, Core, 5/6)
I don't think that works. That would alert you about the security alerts on the Security tab of the dotnet/announcements repo, which are empty, not about issues that contain information about .Net security issues.
-
.NET: Modelo Criptográfico, lo que necesitas saber.
.NET Core 2.0 Cryptography uses Apple Security Framework on macOS · Issue #21 · dotnet/announcements (github.com)
-
Situation right now
Yeah, it's a fun meme, but there have been a few nasty RCE vulnerabilities patched on .NET Core in the last couple years. Like this one: https://github.com/dotnet/announcements/issues/178
-
.NET Core 2.1 container images were deleted from Docker Hub!
If you started receiving errors when pulling old versions of dotnet docker images (like the .NET 2.1), it's because Microsoft deleted them from Docker Hub on August 21st, 2021. That date is not a coincidence, the .NET Core 2.1 reached end of support in the same date. For more details take a look at the official dotnet announcement or also the dotnet blog. In my case, the error bellow was thrown in the stdout when pulling the microsoft/dotnet:2.2-aspnetcore-runtime image:
-
Are you using .NET on Arch Linux? Is the experience good?
I'm not entirely sure what that means. We're done porting .NET Framework APIs to .NET Core / .NET 5. .NET Framework is what it is now, and .NET is moving forward with .NET 6+. If it is worth porting your code to .NET 6, it is. If not, then it isn't. Both can be good choices. .NET Core on Linux, however, is absolutely not preview.
- NuGet package restore broken on .NET 5+ with Removal of Trust of Verisign CA
.NET Runtime
-
The search for easier safe systems programming
.NET has explicit tailcalls - they are heavily used by and were made for F#.
https://learn.microsoft.com/en-us/dotnet/api/system.reflecti...
https://github.com/dotnet/runtime/blob/main/docs/design/feat...
-
Arena-Based Parsers
The description indicates it is not production ready, and is archived at the same time.
If you pull all stops in each respective language, C# will always end up winning at parsing text as it offers C structs, pointers, zero-cost interop, Rust-style struct generics, cross-platform SIMD API and simply has better compiler. You can win back some performance in Go by writing hot parts in Go's ASM dialect at much greater effort for a specific platform.
For example, Go has to resort to this https://github.com/golang/go/blob/4ed358b57efdad9ed710be7f4f... in order to efficiently scan memory, while in C# you write the following once and it compiles to all supported ISAs with their respective SIMD instructions for a given vector width: https://github.com/dotnet/runtime/blob/56e67a7aacb8a644cc6b8... (there is a lot of code because C# covers much wider range of scenarios and does not accept sacrificing performance in odd lengths and edge cases, which Go does).
Another example is computing CRC32: you have to write ASM for Go https://github.com/golang/go/blob/4ed358b57efdad9ed710be7f4f..., in C# you simply write standard vectorized routine once https://github.com/dotnet/runtime/blob/56e67a7aacb8a644cc6b8... (its codegen is competitive with hand-intrinsified C++ code).
There is a lot more of this. Performance and low-level primitives to achieve it have been an area of focus of .NET for a long time, so it is disheartening to see one tenth of effort in Go to receive so much spotlight.
-
Airline keeps mistaking 101-year-old woman for baby
It's an interesting "time is a circle" problem given that a century only has 100 years and then we loop around again. 2-digit years is convenient for people in many situations but they are very lossy, and horrible for machines.
It reminds me of this breaking change to .Net from last year.[1][2] Maybe AA just needs to update .Net which would pad them out until the 2050's when someone born in the 1950s would be having...exactly the same problem in the article. (It is configurable now so you could just keep pushing it each decade, until it wraps again).
Or they could use 4-digit years.
[1] https://github.com/dotnet/runtime/issues/75148
-
The software industry rapidly convergng on 3 languages: Go, Rust, and JavaScript
These can also be passed as arguments to `dotnet publish` if necessary.
Reference:
- https://learn.microsoft.com/en-us/dotnet/core/deploying/nati...
- https://github.com/dotnet/runtime/blob/main/src/coreclr/nati...
- https://github.com/dotnet/runtime/blob/5b4e770daa190ce69f402... (full list of recognized keys for IlcInstructionSet)
-
The Performance Impact of C++'s `final` Keyword
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
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
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
https://github.com/dotnet/runtime/issues/59591
Support zstd Content-Encoding:
- Writing x86 SIMD using x86inc.asm (2017)
-
Why choose async/await over threads?
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
What are some alternatives?
netcoredbg - NetCoreDbg is a managed code debugger with MI interface for CoreCLR.
Ryujinx - Experimental Nintendo Switch Emulator written in C#
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
CoreCLR - CoreCLR is the runtime for .NET Core. It includes the garbage collector, JIT compiler, primitive data types and low-level classes.
actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.
jellyfin-server-freebsd - jellyfin-server component for freebsd
WASI - WebAssembly System Interface
jellyfin-skiasharp-native - SkiaSharp Module for Jellyfin
SqlClient - Microsoft.Data.SqlClient provides database connectivity to SQL Server for .NET applications.
vgpu_unlock - Unlock vGPU functionality for consumer grade GPUs.