Never say never We‘ll see when Unity will also move further towards .NET 5, especially because of the platform support they don‘t have to deal on their own anymore.
I don‘t expect it to happen any time soon, and I‘m patient enough to wait as long as I have to. :)
Unity is heavily invested in a game optimized version of .net. That won’t change. They do use the Microsoft Rosetta compiler to generate their intermediate representation. The runtime and low level compilers are custom. Mono is used for debug builds.
Any realistic Swift interop will probably be for UWP/ Xamarin / or .net core.
I do not question your knowledge and believe you. It's just a wish-thinking of mine that one good day I will be able to script a few tiny games in Swift and have a great engine like Unity under the hood.
Having an official Swift interop in C# is the first right step.
I don’t really understand why, but game engines are normally built like platforms instead of libraries. That makes them weird to integrate with. Godot is probably the easiest popular engine to build bindings for, but it also takes the platform approach.
I’m really interested to see how realitykit has advanced since last year. There is evidence of a visual shading language under the hood in Catalina. There is a chance it might not be missing any tent pole features this year.
C bindings can be created (by hand) for C++ libraries, right? If I could get this working, I'd be so excited. Windows GUI/desktop application development with Swift using Fluent is the dream. I might have a fun project ahead of me
FWIW, I did not intend my reply as mockery, but merely to say that she chance of Microsoft abandoning their own (actually quite good) language tool chain for a solution "not invented here" is about the same as that of a snowball in hell on a very warm day...