Hahaha, and that you think makes more business sense than just licensing the patents (tens of billions vs tens of millions of $$)? I'm sure Apple stockholders are glad that you aren't running the company.

Yes it is, anybody can sign up for a free ovi.com email account. Nokia employees generally have a @nokia.com email address.

What is "truely" native? What are the other kinds of native code? NDK allows you to build native applications that execute directly on the processor, as opposed to inside Dalvik, that's native in my books. Moreover, if you make your UI in OpenGL you don't even have to use Android UI elements.

Either that or he just happens to have signed up for a free ovi.com email account.

I would hardly call making available an XML file with a list of songs and playlists, as means of interoperability with iTunes. Maybe you're confusing it with iPhoto, which actually does allow interoperability with various cameras and devices. Like iPhoto, Mac OS X's default music management application, iTunes, too needs to be device neutral (especially when it can be achieved by simply NOT blocking devices based on USB vendor IDs).

I think, this type of application behavior only makes Apple look insecure. People will still buy iPods and iPhones, regardless of whether iTunes allows syncing with other devices.

I'd be surprised if Excel was compiled using gcc :)

Unless XBMC was trojan installed on your Xbox, I'd say the Xbox is hardened.

You could use a caching controller, which would handle view caching logic.

By that logic, Apple software should come with no EULAs or Terms of Use as well. Far more people would read (and comprehend!) a dialog message informing them about phishing security than the 10,000+ word EULAs that many Apple applications come with.

Which hindrance of the two do you think is more useful and has better usability? It's pretty obvious that this omission has absolutely nothing to do with usability.