Apr 09 2010
Apple shows fear
Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).
The above new restrictions are part of Apple’s EULA for the forthcoming iPhone OS 4 SDK. This restriction is designed to destroy competing development tools like Adobe’s Flash CS5, Novell’s MonoTouch or Unity Technologies’ Unity for iPhone. All of those tools use technologies and programming languages that have not been designed by Apple and are out of Apple’s control. And they all have in common that they either already are cross platform tools or can easily be enhanced to become cross platform tools that could deploy the same application on Google Android or Microsoft Windows Mobile. The competition uses more modern and easier to learn programming languages (for example C# or ActionScript/JavaScript) than Apple’s own Objective-C. And if I might say so, they also have much more advanced Integrated Development Environments than Apple’s Xcode is.
So, naturally, Apple is afraid. And once more, instead of trying to innovate, compete and be better than the competition, they try to build another legal Chinese Wall around their little garden, close their eyes and just shut off everything that they do not want to see.
That approach might work in the consumer market for a little while. But developers hate being restricted, they had being dictated and they will simply step out of this little Apple prison and move on to the next best thing that is open, welcomes them and lets them do and use whatever they want.
In other words, Apple will successfully kill itself with this new set of restrictions and will push the developers to Google’s Android platform. Android is OPEN. There is no content and programming language censorship. It is FREE.
Another thing that I could imagine is that Adobe might respond to this attack on their Flash platform by dropping their support for Apple’s Mac OS X platform. They could offer free crossgrades to the Windows versions of their applications to their existing Mac OS X customers. Maybe even negotiate a deal with Microsoft for subsidized Windows licenses – after all, all Macs that were produced in the last couple of years can run Windows.
This would be a GAME OVER message for Apple’s last niche in the professional market. Maybe Apple wouldn’t care much; after all, they’ve become a consumer company anyway and Steve Jobs already said more than ten years ago that Apple had lost the desktop war, that the Macintosh platform is dead and that Apple should focus on the next big thing – which, as it turned out, would be mp3 players and mobile phones. The Mac is no longer really important for Apple, and hasn’t been for several years. From Apple’s perspective, the Mac only has two roles left: It’s the development tool and home (content) server for the iPhone/iPod/iPad product lines – which, along with the iTunes store, are their real cash cows. The moment the iPad becomes powerful enough to be its own development machine, the Mac will be discontinued – just like the Lisa was killed when the Mac became mature enough.
Still, this new EULA restriction is going to hurt Apple. They don’t understand developers.