Steve Troughton-SmithOct 27
Keep going and do Xcode
https://mastodon.social/@daringfireball/115447175725037606
Show threadJohn GruberOct 27
@stroughtonsmith Updated!
Show threadCraig HockenberryOct 28

@gruber @stroughtonsmith I suspect the problem with Xcode isn’t development work, but rather with entitlements.

Allowing Xcode on iPad would mean that a user process would have access to another user process (for debugging). Same with hardware for things like USB ports.

Look at the current Xcode entitlements to see the scope of this problem. It’s a security issue that they want to isolate on the Mac.

Show threadSteve Troughton-Smith
@chockenberry @gruber entitlements are just arbitrary gates added on top of system APIs to stop third party developers from using them. Swift Playgrounds on iPad has a ton of them too. I don't think entitlements meaningfully impact a decision to put Xcode on iPad
Oct 28 at 9:56pmIvory for Mac
Show threadCraig HockenberryOct 28

@stroughtonsmith @gruber I haven't played with them enough, but are they able to do things a normal Simulator isn't able to do?

I'm wondering about accessing biometrics, USB, and other "device only testing" things.

I'm having a really hard time imagining Apple Security saying "yeah, why not?" to sensitive parts of the system.