Not really… I have tried it before on an m1 iPad. It is not usable for any windows version. XP for example takes over 15 minutes just to boot. It takes multiple seconds for clicks to register, etc.
Linux, like Debian for example, will be much more usable, but still far from anything you would call a smooth experience.
Again, not having JIT really kills the performance here.
because its not about jit per se, its about marking pages of memory as executable. doesn’t matter whether you compile it or load it from disk, you need to mark the memory as executable so the cpu will run it, and that isnt something “normal” ios apps are allowed to do.
@neme I like how the devs were like “eh, it’s not even that good of an app, whatever”
Yeah well because Apple doesn’t allow JIT compilation, so the performance would’ve sucked anyway.
I’d guess Windows for Arm would perform fine though.
Not really… I have tried it before on an m1 iPad. It is not usable for any windows version. XP for example takes over 15 minutes just to boot. It takes multiple seconds for clicks to register, etc.
Linux, like Debian for example, will be much more usable, but still far from anything you would call a smooth experience.
Again, not having JIT really kills the performance here.
Why is a jit needed for native arm software?
Because ARM is not the same as ARM. Windows arm does not natively run on an Apple M1 Processor and MacOS does not run on a raspberry pi.
because its not about jit per se, its about marking pages of memory as executable. doesn’t matter whether you compile it or load it from disk, you need to mark the memory as executable so the cpu will run it, and that isnt something “normal” ios apps are allowed to do.