4 ms·
As a prospective (licensed but unreleased) developer, I don't care about this particular rule, because I'll be working directly in XCode. I do care about how A
by CamperBob 17y ago
As a prospective (licensed but unreleased) developer, I don't care about this particular rule, because I'll be working directly in XCode. I do care about how Apple sprung it on their developer community out of a clear blue sky, trashing a lot of peoples' hard work in their quest to hose Adobe.
If Apple doesn't mind taking a wrecking ball to Unity3D's business model, who's to say they won't come up with some crazy rule next year that prohibits something I'm doing? How can I build a healthy long-term business around iPhone/iPad development, when I could find myself on the wrong side of a turf war I didn't even know was being fought?
- akadien 17y agoI'm in the same boat. I know obj-c, but wanted to use unity3d for a game and phonegap to leverage my html5/CSS skills. Now, I'm spooked by what I perceive is Apple's prerogative to be arbitrary. I understand needing to cull the 'crapps', and that cs5 may have been the target. But why use carpet bombs when a scalpel would have done the job just as well?
- snom370 17y agoSame boat here. For me, this is a really touch choice. I like the SDK and I think the iPhone OS is by far the best mobile OS out there, but I'm not sure I want to back this horse. When Microsoft was the Evil Empire it was easy to stay away from them because I didn't like their software, but it costs me something to stay away from Apples ecosystem since it's really good. But I'd much rather see the mobile web succeed than the App Store and the other closed ecosystems.