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…
"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)…
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.…
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…
"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)…
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.…