It's not malicious to build a game or a music app. What I'm saying is that before you hand out tools to do that, you have to at least think about what else those tools can do. Microsoft has been repeatedly burned by this, cf Raymond Chen http://blogs.msdn.com/b/oldnewthing/archive/2005/06/07/42629... , and it's a very, very basic principle of platform/API design.
I argue that Apple's focus on the user experience, especially in the areas of responsiveness, battery life, and consistency with the general Apple design aesthetic, cause Apple to make choices here that you disagree with, but which aren't necessarily bad decisions.
"You can build music, and video, and game web applications on those devices without these limitations, and it is not a problem."
Actually it is a problem: Android malware exists, and I say that it proves my point: if you hand out capabilities without thinking through the consequences, it will come back and bite you.
The uses that you intend for tools are never the only possible uses of those tools.
I argue that Apple's focus on the user experience, especially in the areas of responsiveness, battery life, and consistency with the general Apple design aesthetic, cause Apple to make choices here that you disagree with, but which aren't necessarily bad decisions.
"You can build music, and video, and game web applications on those devices without these limitations, and it is not a problem."
Actually it is a problem: Android malware exists, and I say that it proves my point: if you hand out capabilities without thinking through the consequences, it will come back and bite you.
The uses that you intend for tools are never the only possible uses of those tools.