.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
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).
exploring faster code generation techniques that take advantage of the JIT's de-virtualization and in-lining
Build time-series-based applications quickly and at scale.. InfluxDB is the Time Series Platform where developers build real-time applications for analytics, IoT and cloud-native services. Easy to start, it is available in the cloud or on-premises.
A source generator for minimal APIs
They are source generated version of what ASP.NET does today (in both MVC and minimal APIs). There are some ergonomic challenges with source generators that we'll likely be working through over the coming years so don't expect magic. Also its highly unlikely that ASP.NET Core will not depend on any form of reflection. Luckily, "statically described" reflection generally works fine with NativeAOT.
Things like configuration binding, DI, Logging, MVC, JSON serialization all rely on some form of reflection today and it will be non-trivial to remove all of it but we can get pretty far with NativeAOT if we accept some of the constraints.
As of right now, we're trying to make sure "motivated people" can play with it, but it's not something that is supported by ASP.NET Core or EF at the moment.
ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
This repo is the official home of .NET on GitHub. It's a great starting point to find many .NET OSS projects from Microsoft and the community, including many that are part of the .NET Foundation.
Bookmark https://devblogs.microsoft.com/dotnet/ and read occasionally. https://docs.microsoft.com/en-us/dotnet/csharp/whats-new/csh... is good for a quick overview of language features depending on what version you're at.
Most .NET devs only need to be peripherally aware of these changes, as most businesses using .NET will move slower than Core's new pacing. It's even less important for lower seniority devs as you typically need project changes to utilize new features, which is a call a senior would make, which involves approval/testing/deployment, so a slow process which gives you time to read up on the new features as they're needed.
You're better at your "craft" the more tools you know about and how to apply them, but if your day job prevents you from following the new stuff, I wouldn't worry too much about it.
>I feel .NET Core after a good start is falling into the typical Microsoft trap of constantly cranking out new stuff to do the same thing and leaving it to developers to keep up.
Yeah, the pacing has increasing dramatically from .NET Framework days, but that's probably a good thing. I would just stick to learning about what you do in your day job. .NET has a huge ecosystem compared to other languages, so it's going to be very hard to keep up with everything MAUI is doing if you're doing regular ASP.NET core APIs.
Powerful .NET library for benchmarking
Many of the benchmarks are using BenchmarkDotNet, so consider reporting this to them: https://github.com/dotnet/BenchmarkDotNet/.
.NET 8 Blazor Planning!
3 projects | reddit.com/r/Blazor | 9 Dec 2022
Frozen collections in .NET 8
3 projects | reddit.com/r/dotnet | 28 Nov 2022
Should I prefer IHostedService over Task.Run(...)?
2 projects | reddit.com/r/dotnet | 9 Sep 2022
WASM Threading and exception support is coming to C#
2 projects | reddit.com/r/Blazor | 30 Jun 2022
When it comes to microservices, do you put each microservice in it's own git repository, or use a monorepo? If the same, how do you handle multiple services in the same repo? Keen to hear your thoughts
2 projects | reddit.com/r/dotnet | 25 Apr 2022