I'd say it's pretty obvious that this is a desired outcome on Apple's part. You can either wait until it's too late or bring it up before it's happening.
I'd say it's pretty obvious that this is a desired outcome on Apple's part. You can either wait until it's too late or bring it up before it's happening.
Over the years, Mac's defaults have changed to protect inexperienced users via restrictions like Gatekeeper and SIP. Apple has never attempted to make any of these systems mandatory. All it takes is a few terminal commands to gain complete kernel-level access to my system.
Because companies never lie or say that "we're not going to do XYZ" until next week/month/year where they go "XYZ is the new awesome". Expecting companies to be honest is like placing a cat near a canary and expecting them to be BFFs, especially when the topic is something that people have negative concerns about.
It is MUCH better to be explicit and loud about what you do not want to see before it happens, than try to reverse a situation after it has already happened. You lose nothing by doing the former, even if there were never plans to do what you fear might happen.
100% of the projections I've seen about MacOS becoming a walled garden have been from people that don't actually have any real familiarity with Apple's ecosystem as developers.
macOS is a more open platform because Apple has decided to leave it that way, not because the property is literally essential for development.
(That's actually the funniest part about all this, now that I think about it. While everyone is wailing and gnashing their teeth about some speculative possibility that macOS ends up locked down like iOS, Apple has been making iOS more open.)
They are also not going to allow any Electron apps?
No, I don't, double check which commenter you're replying to. :)
I'm just arguing Apple could lock down macOS if they wanted to, without making iOS development impossible.
This is exactly what I'm talking about. You're using bad or outdated second or third-hand info with no regard for the game of telephone involved in getting it to you, nor the anti-Apple zealots obfuscating the truth on its way.
What I do know is: if you try to use more intensive emulators like PPSSPP on a non-Jailbroken iOS device (via a developer account, enterprise cert, or similar), you will not get acceptable performance, because the emulator is forced to fall back into an interpreter mode.
Even on Jailbroken devices, the hacks required to make JIT work cause weird issues: https://github.com/hrydgard/ppsspp/issues/9186
I’m not even going to try and address whatever weird issues a console emulator might have, those always have problems being ported to non-x86 platforms, especially when they include a JIT. As it happens, dynamic recompilation of machine code not designed for that purpose can be pretty damn hard. Take a look at the posts the Dolphin emulator team make about the fun they encounter.
This isn't that! The JIT works when you remove iOS's sandbox (by Jaibreaking). And this applies to every iOS console emulator.
I don’t see that. Why do you think it will happen?