themesof.net VS dotnet-buildtools-prereqs-docker

This is a good one, though it's more vague then a typical roadmap https://themesof.net/

Right, so, if we're going to talk about unreleased, future features, then I have a little roadmap here to show you.

The dotnet team at least does use it in a number of stuff. Tye's dashboard UI uses Blazor server, and if I recall some parts of MS docs uses Blazor WASM to evaluate C# code in the browser. dotnet live and https://themesof.net/ uses Blazor server as well.

Having said that, charting is a very basic and fundamental enterprise application requirement, so we do support that. As a matter of fact we have an entire project theme (inspired from https://themesof.net/) dedicated to enterprise solution requirements, including lot of stuff from async queue-based or batch processing to allowing the end user to define their own queries and exporting results to excel and the like.

What you call "meme", I call .NET appeals to net-new developers, students, and new technologists, which is one of the Themes of .NET, which guide the platform, languages, and tooling roadmap.

There’s more information on the plans, changes, and challenges encountered with the current .NET 6 development on Microsoft’s Themes of .NET.

The Microsoft .NET 6 development team clarified that containers are a daily focus of the group, both as the basis of the build infrastructure and as a product scenario. They noted that even current .NET performance testing uses containers. This is due to the multiple projects planned for improving containers in .NET 6. Some of these planned improvements include: