ASP.NET Core VS .NET Runtime

2) do much more frequent minor updates - keeping nuget packages up to date say monthly, major lib updates like asp.net every couple of years etc (dont need to follow bleeding edge changes)

I have been pulling my hair why such an easy thing to do in other frameworks like asp, or asp.net (hello session variable),is soooo difficult in react. Ok so how do I share state from one component to another component. I tried callback but no do. Now I am trying context. But is redux is the one that I should use?

You've chosen the backend, ok so all you need is a c# and little bit of the asp.net core, maybe razor pages. Honestly C# is the point, all the web related part is the matter of 1 day reading.

ASP.NET: https://github.com/dotnet/aspnetcore/issues/44984

Recently, a lot of effort has been put to simplify the dev experience, so as r/gatnoMrM told you, you have to specify the version you are working with. My go to when working with .NET is to figure out the class that I'm looking for, and then in the .net docs for the class for my target version, look at the api signature and perhaps, if it's a commonly used class, it would have suggestions as well or it will tell you alternatives.

Take a look at this issue in the dotnet/aspnetcore repo, it seems to be the problem you're hitting:Access violation/StackoverflowException in new .NET6.0 WebAPI application

I use it all the time for scripting. And i use Visual studio for asp.net or c#. But code does do C# pretty well, I sometimes use it when working on Unity C# scripts.

Take a look at hosted services and see if its a good fit, I dont have experience with it in a library but its good for background tasks in a asp.net core webapi app

well for http just make it in to a asp.net core app and for message queue depends on the one you want to use

This issue is still open: https://github.com/dotnet/runtime/issues/35995

Also, it seems that initial memory settings have a big effect on mobile, this is a fix that will make it for 7.0.4 (April): https://github.com/dotnet/runtime/pull/80849

looked it up and engine.cpp seems to only be 8.5k lines, which doesn't seem super unreasonable to work with. It ain't no gc.cpp that's for sure.

Threading.Channel has more or less replaced all the concurrent queue alternatives for me. channels have the benefit of nonblocking wait for when the channel can be written.

My teammate created an issue on GitHub: the developers fixed the order of arguments and added a test.

i have tried with an adapted .editorconfig but even using the "official" dotnet team editorconfig

Technically Mono supports RISC-V, so you can get .NET code running on it. Also it looks like if you're willing to go through messy and poorly documented build processes you can build CoreCLR on RISC-V: https://github.com/dotnet/runtime/issues/36748

So proper support is likely coming soonish, I'd guess by the time .NET 8 comes out.

There's an issue on simplifying WebSockets specifically https://github.com/dotnet/runtime/issues/77060 that may be of interest.

See CLR is also using left/right for its not-quite-binary-tree in SortedSet. Though this also uses the Enum-As-Discriminator trick instead of boolean/array. I know the JVM also has/uses left/right but I can't find the backing source file right now.