04-10-2010, 05:35 AM
Article Accelerator wrote: Not quite that simple. First, Theora is a sub-optimal video codec:
http://en.wikipedia.org/wiki/Ogg_theora
"It supports intra-coded frames and forward predictive frames, but not bi-predictive frames which are found in H.264 and VC-1. Theora also does not support interlacing, or bit-depths larger than 8 bits per component."
Oh no, only 8 bit per component. How many of us have monitors that support more than that?
Article Accelerator wrote: Apple's problem with Flash are many and varied, Suzanne. Flash is a prime source of security and stability problems. It is also a processor hog and that, in turn, leads to excess power consumption and heat. While processor hogging is significantly more serious on the Mac platform, Flash implementations on Windows encounter the same issues.
And all those problems can be created by the technologies Apple allows on the iPhone. JavaScript is often worse than Flash, but most people aren't knowledgeable on the subject to discover that.
To reiterate, those problems can be created by poor Flash development, just like they can be created by poor C++, JavaScript... development.
Apple, on the other hand, is promoting open standards in general and, in particular, the open HTML5 standard as a specific replacement for Flash technologies.
Please explain how you can honestly say that. As previously discussed, H.264 is not open, nor a standard. Apple is pushing H.264, it's not an open standard...
Apple is pushing yet another proprietary solution on us. Many years ago we were fighting the battle with Windows Media, and it not playing on Macs. And also RealPlayer, and its general relegation of Macs. Finally Flash started playing video and it worked on multiple platforms. It took off, and now the majority of video on the web is Flash.
Article Accelerator wrote:
[quote=M A V I C]
[He just doesn't support it on the iP* devices. Some have said it has to do with user experience, but actions they put into place yesterday don't align with that.
Yes, they do. As I cited before,
http://news.ycombinator.com/item?id=1250946
"Adobe's Flash compiler is a classic maneuver to "commoditize your complements," as Joel put it so well. Apple don't want to be commoditized, especially if it means having apps that don't take advantage of the iPhone's strengths."
[ my emphasis ]
Your citation isn't relavant. If Apple's goal was to enforce some sort of QA on user experience, they could have just put that in the EULA. They also enforce this in their general app approval process by forcing people to use the AppStore.
They make a EULA change that was different than that. It excludes any interpretation layer regardless of the user experience it creates. An interpretation layer can take advantage of the iPhone's strengths.
If using third party development tools always equaled poor user experience, your assertion may be correct. But since it doesn't equate and because Apple didn't make the EULA change about user experience, it should be clear that Apple has other motives.