On the contrary, it was quite civil and thought provoking. It was simply terse, elegant, and to the point. "Naive" needn't have been interpreted as a personal attack, it was a sufficient and complete summary of the argument presented, implying it undeserving of response. Only lack of creative imagination would consider "Naive" not thought-provoking. It is not my responsibility to hand-hold and lead a conversation. If someone cannot immediately mentally extrapolate the implications of a statement, maybe they should ponder it and explore the possible meanings, giving me the benefit of the doubt as to poignancy. Instead, they vote it down, because it's not full of the superficial spoon-fed explicitness the down-voters expect.
I got -4 karma points on this, for refusing to answer point by point the arguments of a naive Apple fanboy. I'll go back to just scanning HN, instead of participating. I've been a professional programmer for over 30 years, Written for Macs since 1984, I know what I'm talking about, and I find the current generation of developers to be, well, babies.
Incidentally, I just tried the latest "fastest ever" Google Chrome with this. The frame rate DROPPED on my machine from 48fps to 18fps. I'm getting the feeling that pushing the performance limits of compiled JavaScript is not an effective endeavor right now.
You presume too much. Think, man. Free high-performance HTML5 web apps are 1) not under their control and 2) not profit-making for Apple, as they bypass the App Store.
The reason that it IS a BFD is that Steve Jobs is now saying they have "high performance HTML5" on iPad. This is evidently not true. Here is an app for which it makes a big difference, something I prepared on my MacBook Pro (with the iPad in mind) only to be pwned by Apple's anti-competitive exclusion of the JS JIT compiler from iPad Safari: http://grokware.com/ff.php