Xcode running on the iPad would not be a suitable replacement or stand in for Xcode on the Mac; it doesn't need to. There are two use cases where having Xcode on the iPad serves a much needed need:
Testing and immediate feedback for developing apps utilizing the built-in Lidar and AR features.
Testing with live feedback for apps involving location based experiences (making use of GPS).
It’ll happen. The iPad Pro is 100% capable now to host real pro apps.
Xcode isn't a "pro" app. It's a developer tool.
I think Prosser and plenty of other non-developers have conflated "building for iOS" and "building for ARM", and I'd be willing to bet that's what's going on here. Especially with Prosser's language. "present on iOS".
Present? That's a weird way to put it. Present on ARM builds of macOS reads better.
Prosser has this odd habit of saying he's not entirely sure about something and then saying he's absolutely certain of that thing in the next sentence, and then taking credit for being first. All while saying he's just an entertainment site. He doesn't understand the deeper issues and he covers that by apparently assuming there's no depth to it at all.
As for developer tools, Apple has already been enhancing Playgrounds on iPad at a pretty good clip so far, and if they're going to host developer tools on iPad OS they'll likely come at it with a large contribution from that side and meet in the middle, at some space in between Playgrounds and current Xcode.
Development is not just a lone person sitting in front of a machine writing code, even when it's just a lone person sitting in front of a machine writing code. There's testing and integration and often a lot of these things are automated to some extent. And that's only some of what the developers in this article are talking about.
Xcode is a tool for professional developers. It’s a pro app.
Perhaps we can look to the much simpler problem of adding an cursor, trackpad nd mouse to an iPad (and iPhone). Apple simply, didn’t exhibit any interest in this since the beginning, at least publicly. Then they gave us a primitive c]version in Accessibility. They watched the responses.
NO. They provided Accessible input to those who had difficulty with direct touch input to the screen. Period.
Perhaps we can look to the much simpler problem of adding an cursor, trackpad nd mouse to an iPad (and iPhone). Apple simply, didn’t exhibit any interest in this since the beginning, at least publicly. Then they gave us a primitive c]version in Accessibility. They watched the responses.
NO. They provided Accessible input to those who had difficulty with direct touch input to the screen. Period.
What an incredibly benighted attitude.
So dramatic, rolleyes. No, what Mel is saying is the pointer functionality evolved. And it’s reasonable to expect other technology will start simpler and evolve. It’s a perfectly reasonable musing.
It’s the way Apple usually does it. It’s the same thing for opening up their newest technologies. First, they keep it for themselves. It’s not greed, as some like to say, but rather the concept that they can wring out the features best themselves for a year or so. Then they release some of it to developers, then if useful, they release the rest.
its just too difficult to do a full featured upgrade all at once. Imagine if Adobe tried to release the current version of Photoshop in 1990. Or if Apple had tried to release 10.5 in 2000.
Comments
its just too difficult to do a full featured upgrade all at once. Imagine if Adobe tried to release the current version of Photoshop in 1990. Or if Apple had tried to release 10.5 in 2000.