Any idea how Apple might handle a dilemma like that ?
Check out this article about why Apple doesn't bother with expensive distracting public concept products.
http://counternotions.com/2008/08/12/concept-products/
Apple's products have a bit more cross-platform functionality than Corning's at this point in time. Unless you consider transparency a cross-platform feature.
My question is how will Apple deal with the disruptive potential of cross-platform ? It's hard to believe Apple will not be challenged by it.
And somewhat related. What's the input language going to be? Or will it be a tool that converts to one language?
The web. That's why Apple has been working to make sure that Safari was standards-compliant, if "cross-platform" is going to be the future, it will more than likely happen via the web. So long as Apple can maintain a standards-compliant browser, then can compete on the web and spend their energies making sure the other aspects of their products (design, battery life, etc) are competitive.
Isn't that how iPhone development was supposed to happen? Then everyone whined and complained that they wanted a native development system. Now that they have it (and it's a pretty solid one), we're supposed to whine that it's not cross-platform?
I'm guessing HTML5 and etc will help solve that problem, correct?
I don't see any great 'cross-platform' environments out there other than the web, and Apple is one of the leaders in developing that.