> "Since iOS 13.3.1, it appears Apple has stopped allowing free developer profiles to sign dylibs." A terrible decision. Users should always be allowed, at the very least, to build and sideload their own code .
QEMU for iOS
21–30 of 150 posts
Re: QEMU for iOS
#22This is cool, but I can't help but think that running a VM on an iPad or iPhone would be horrendously slow.
Re: QEMU for iOS
#23Re: QEMU for iOS
#24This is cool, but I can't help but think that running a VM on an iPad or iPhone would be horrendously slow.
The iPad Pro is very impressive, here a video of one playing Half Life 1 in XP using UTM [0] [0] https://www.youtube.com/watch?v=O19dNVTBCAs&feature=youtu.be
Re: QEMU for iOS
#25Earlier quoted context omitted.
> 2.5.2 Apps [may not] download, install, or execute code which introduces or changes features or functionality of the app, including other apps. The rule changed, I think around the time that Swift Playgrounds came out, to add: > Educational apps designed to teach, develop, or allow students to test executable code may, in limited circumstances, download code provided that such code is not used for other purposes. S…
There's no legal risk. Microsoft allows people to install emulators on their OS without issue. The issue is that Apple wants a big profit cut on each app. If you were allowed to download & run applications on your own computer, then Apple wouldn't get its cut.
Microsoft "allows" people to install emulators in the same sense that Apple "allows" it on macOS, but a quick search confirms that Microsoft does not allow emulators on their app store, nor does Google. (These policies may specifically be for video game emulation, which is mostly what the legal grey area covers.)
Re: QEMU for iOS
#26Re: QEMU for iOS
#27> "Fast native graphics through para-virtualization thanks to SPICE" I'm assuming the SPICE referred to here is not the SPICE I know, unless they've gone the full video circuit emulation route, which I don't imagine being fast at all :)
Re: QEMU for iOS
#28An interesting exception to this is Expo, an app that lets you load React Native apps built by other developers over the internet. Expo gets around this on Apple by forcing you to sign into that developer's account before downloading their app, so that it's plausibly "yours". I've used to distribute early builds of a React Native app really easily.
All of this to say, I wonder to what degree Apple's policy applies when it's "your" app, or you are the developer, or whatever. I suspect Expo, as a venture backed startup, has some kind of a working relationship with Apple that affords them a tiny amount more leeway than the average Github user.
This could actually be an incredibly useful application that many people pay lots of money for if were ever allowed on the market -- think of the combination of iPad + keyboard + Windows Remote Desktop. Really sad that Apple makes their platform so restrictive. (Yes, security issues, but still, seems like a good enough sandbox could overcome the danger of remote execution.)
Re: QEMU for iOS
#29Not being in the apple world I wondered if this submission meant anything had changed regarding running stuff like this on iOS, but no: > Why isn't this in the AppStore? Apple does not permit any apps that has interpreted or generated code therefore it is unlikely that UTM will ever be allowed. However, there are various ways people on the internet have come up to side load apps without requiring a jailbreak. We do n…
> 2.5.2 Apps [may not] download, install, or execute code which introduces or changes features or functionality of the app, including other apps. The rule changed, I think around the time that Swift Playgrounds came out, to add: > Educational apps designed to teach, develop, or allow students to test executable code may, in limited circumstances, download code provided that such code is not used for other purposes. S…
Re: QEMU for iOS
#30> Apple does not permit any apps that has interpreted or generated code An interesting exception to this is Expo, an app that lets you load React Native apps built by other developers over the internet. Expo gets around this on Apple by forcing you to sign into that developer's account before downloading their app, so that it's plausibly "yours". I've used to distribute early builds of a React Native app really easil…
They also get around the limitation of having half the screen showing the executed code by not letting users modify the code through their app.