SirIntruder

Sorry for a complete tangent - I've been assuming gray OP's text in ask/show meant people were downvoting a post and it always weirded me out - now had to double check to confirm it's simply always grayed out (why though?)

IL2CPP is separate concern from how fast Unity performs in editor. Our best hope for better editor performance is they move the editor to modern dotnet, and it's actually quite possible this happens by 2023 cyclus [1]

For domain reload performance, 30s seems really a lot, I suggest you profile InitializeOnLoad calls in the editor - some 3rd party plugins have a nasty habit of clogging domain reload with stupid "check for updates" http calls and similar junk, I found it rather easy to clean up.

[1] - https://forum.unity.com/threads/unity-future-net-development...

"It is amazing how complete is the delusion that beauty is goodness." - Lav Tolstoy

It definitely uses x86 emulation, if that's what you mean. But based on the these M1 threads I would expect M1 x86 emulation to work like magic, not be 5 times slower than some dual core 2016 model.

I'm curious if anybody tried AppleM1 with Unity3D? This guy reported dreadful compilation performance (11.6s on AppleM1 vs 2.3s on some old dual-core 2016 Intel model) https://forum.unity.com/threads/unity-compilation-speed-is-s...

There is already a scripting dialect of c#, that seems mostly used in some web apps and for learning purposes. So they want to "streamline" this aspect, because currently this dialect requires a lot of custom handling. https://github.com/dotnet/csharplang/issues/2765