So... What does this have over using NativeAOT which already exists?
Keep in mind a large portion of time NativeAOT is actually SLOWER than going through RyuJIT with the only definitive benefit being smaller binaries, and it's not like you can't do Span<T> and ref structs in modern C# for manual low level memory control already.
So my question is just... why?
My view is that this is mostly for demo-scene style programs. The author of bflat, from which this slop is forked, has some examples on their website of a "2kb game for windows" or "4kb game targeting UEFI" (i.e. no operating system).
https://migeel.sk/blog/2023/12/08/building-bare-metal-bootab...
I would not want to build a long term project on top of this, as maintaining a fork of the .NET runtime is somewhat labor intensive.