By the same metrics, we should evaluate performance of C and C++ code by using benchmarks with MS-DOS C and C++ compilers, which should be about the same age.
Don't mix languages with implementation when talking about performance.
Basically they generate C++ from MSIL as a means to generate native code, instead of building their own compiler backend.
They plan however, to eventually update their Mono runtime.
https://forum.unity3d.com/threads/future-plans-for-the-mono-...
1. Jai is not even released.
2. Jai is a programming language, not a game engine.
Unity is slow because they are using an outdated C# implementation (some old Mono).
Regardless of their GC implementation, in games you don't want opaque runtime behaviour, which a GC always introduces. This leads to weird workarounds in your code that nobody understands instead of having clear and explicit memory management.
C++ became a de-facto standard for games, because console SDKs moved from C to C++, pushed by the companies selling them.
The same companies that are now adopting Unity and have already toyed with the idea of having a C# SDK.
If for the sake of example, PS5 SDK would be C# based, devs that wanted any money from PS5 games would adopt it, regardless of their feelings regarding C++ vs C#.
This is a terrible example and you have no idea what you're talking about.
Is there a way of running C# with reference counting?
Naive implementations are slower than tracing GC, while high performance ones are as complex as tracing GC ones, while having the burden of forcing the developers to explicitly deal with cycles.
I bet there are plenty of game developers who would be only too glad to arrange their references as a DAG, if they could have guaranteed low latency.