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 threadjdotc

@chockenberry @gruber @stroughtonsmith Apple has had a *decade* since the first iPad Pro was introduced to work through these issues. Ten years later, it’s embarrassing that Apple still hasn’t released a version of Xcode for iPad focused on iOS development.

iPad “Pro” marketing has been misleading in this regard for years and has de facto eliminated the amazingly capable iPad hardware as a viable tool for a substantial base of Apple’s professional users.

Oct 28 at 3:41amIvory for iOS
Show threadCraig HockenberryOct 28

@jdotc @gruber @stroughtonsmith Read my toot again.

I’m saying that they can’t do it without compromising the security of the platform.

Show threadjdotcOct 28
@chockenberry @gruber @stroughtonsmith Perhaps. Although I’d suggest that a dedicated version of Xcode for iPadOS and tiered security options in iPadOS Settings.app is significantly less of a platform security risk than the sideloading enabled by DMA in the EU.