If it is 23M pixels per lens, that is still more resolution than a smartphone's screen. Each lens is smaller than a smartphone's screen and the resolution is per eye. I wouldn't be surprised if this actually exceeds the eye's ability to perceive pixels.
The difference between a monitor and the lens of a headset. If you look at a 4K monitor up closely within a region of the screen of two inches in radius, you are not seeing 4K in that region. 4K of pixel applies to the whole monitor not to the eye's field of view as it does to a headset.
If you were using the headset as a monitor, you could zoom in on text and the text can effectively have infinite resolution as it scales up into view.
C# had value types and pointers from the very beginning. These are not a recent addition. The standard library does know about them. However, not until C# 2.0, which introduced generics, were collections able to avoid boxing value types.
There are some cases where allocations are made when they could have been avoided. Iterating over a dictionary creates a single IEnumerator object. Async methods, tuples, delegates, and lambda expressions also allocate memory as do literal strings. It is possible to have struct-based iterators and disposers. There are some recently added mitigations such as a ValueTask, ValueTuple, function pointers, ref structs, conversions of literals to read-only spans, that eliminate allocations.
DateTime is a value type and doesn't allocate memory. Getting the current time does not allocate memory.
With the recent additions to ref types and Span<>, C# provides a lot of type-safe ways to avoid garbage collections. You can always use pointers if need be.
https://www.chess.com/news/view/hans-niemann-lawsuit-dismiss...