04-10-2010, 06:55 PM
Article Accelerator wrote:
Maybe so, but the difference is that javascript is an open development standard under the control of a standards body[..]
True, but that doesn't do anything to disprove my point.
H.264 most certainly is a standard!:
http://en.wikipedia.org/wiki/H.264
"H.264/AVC/MPEG-4 Part 10 (Advanced Video Coding) is a standard for video compression. The final drafting work on the first version of the standard was completed in May 2003.
"H.264/AVC is the latest block-oriented motion-compensation-based codec standard developed by the ITU-T Video Coding Experts Group (VCEG) together with the ISO/IEC Moving Picture Experts Group (MPEG), and it was the product of a partnership effort known as the Joint Video Team (JVT). The ITU-T H.264 standard and the ISO/IEC MPEG-4 AVC standard (formally, ISO/IEC 14496-10 - MPEG-4 Part 10, Advanced Video Coding) are jointly maintained so that they have identical technical content...
If I'm reading that correctly, H.264 is not a standard but MPEG-4 AVC is. They are "jointly maintained" so they're the same, but who's to say that wont change someday? Maybe Adobe will buy it and make it only playable in Flash
You're kidding, right? Can you give me an example of the kind of language Apple should put into its EULA to ensure both performance standards and full compatibility with platform technologies?
It's not worth my time to come up with that, but just about anything written about user experience would be better than what they came up with - IF their goal is to enforce user experience.
If you do, I think you'll find it will read something like that new clause that's caused all this bogus controversy.
So? I'm not saying it wouldn't cause controversy, I'm just saying the way they went about it proves they're not just trying to enforce user experience.
An interpretation layer can take advantage of the iPhone's strengths.
In theory, perhaps. In practice, it has never happened.
I take it you've reviewed every iPhone app? Admittedly, I don't even have an iPhone. I've been hearing developers discuss this topic and they all seem to think some apps don't create any problems by having an interpretation layer.
Keep in mind that one of the main goals of "interpretation layers" or code intermediation is to facilitate cross-platform, i.e. lowest common denominator, application development.
Yep. And that would support deckeda's statement that:
They are telling developers to make a choice now for iPhone vs anything else, unless they want to spend extra time coding for both. None of this was an issue before Android.