enntwo's comments

I assume lacker's point is in reference to the use of the word "Wii" itself, which is clearly a Nintendo trademark. It is not unreasonable that Apple does not want to have an app using a recognizable trademark of another company. And if you read the article, you notice that the reason they were rejected for using Wii, is because Apple felt that it was unrelated to the app, and was used as a keyword to drive search results. (Which was not the case, but from just looking at the keywords is a reasonable response).

The issue the article brings up with Apple is the overall process of such a small issue resulting in an overall 40+ day delay of release due to a poor reviewal process. The article was must less critial of the actual banning of the term "Wii".

You are not limited to developing native apps, in fact, even if you are comfortable in developing in Obj-C, for applications of a certain size using PhoneGap or YUI to make cross-platform WebKit based normal apps is perfectly reasonable.

For apps of significant size or those with performance issues, it is not unreasonable to expect to have to use one native language, such as most game consoles do, or even Android does as pointed out in your link: "If you have performance concerns for your application, it's probably better to use the standard Android SDK (or NDK) where you'll have more control over the system."

Sure you could write a huge app in ASE instead of being restricted to Java, but its not recommended. In the same way you can write a huge app in PhoneGap over Obj-C, but it is not recommended.