this post was submitted on 09 Jun 2024
161 points (96.0% liked)
Apple
17525 readers
32 users here now
Welcome
to the largest Apple community on Lemmy. This is the place where we talk about everything Apple, from iOS to the exciting upcoming Apple Vision Pro. Feel free to join the discussion!
Rules:
- No NSFW Content
- No Hate Speech or Personal Attacks
- No Ads / Spamming
Self promotion is only allowed in the pinned monthly thread
Communities of Interest:
Apple Hardware
Apple TV
Apple Watch
iPad
iPhone
Mac
Vintage Apple
Apple Software
iOS
iPadOS
macOS
tvOS
watchOS
Shortcuts
Xcode
Community banner courtesy of u/Antsomnia.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
@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.