Apple has posted Steve Jobs’ “Thoughts on Flash“. There are a lot of lies and half truths. No one will care. The article has enough valid points that people won’t check up on them.
That said, here’s my attempts to correct the lies.
Lie Â #1: “Adobeâ€™s Flash products are 100% proprietary.”
The Flash IDE, yes. Â The Flash Player, no. Â Here is a list of technologies open sourced/published by Macromedia/Adobe that are in the Flash Player ecosystem:
- ActionScript 3 runtime, called Tamarin. Â Given to Mozilla to hopefully utilize in future browsers.
- RTMP (and it’s ilk), the protocol for real-time video & audio streaming as well as data (AMF).Â Yes, many want “more” open sourced.Â Red5 and Wowza seem to be doing just fine with what is there currently.
- The SWF format itself, which is what Flash Player plays/runs, has most of it’s spec published in case you want to generate SWF files.
This street goes both ways, too.Â Macromedia/Adobe has adopted open source technologies into Flash Player with the hopes of embracing standards, not just the de-facto ones.
- ActionScript 1, 2, and 3 are all based on EMCAScript.Â Yes, it’s not as compliant as many would like.Â Additionally, Adobe did participate in many ECMA Script discussions/debates.Â Yes, 4 didn’t turn out so well for Adobe.
- The XML parsing is based on E4X, ECMA Script for XML.
I’m not saying Adobe’s open sourced a lot of the Flash Player. Â There’s open source, there’s published, and then there is open source.
Regarding their products, he’s wrong there too. Â The Flex SDK, one of the biggest boosts for the Flash Platform in the past 4 years, is also open source (yes, the real kind). Â Most utilize Flex Builder, built on top of the open source Eclipse.
Using a blanket statement saying Adobe’s Flash products are 100%Â proprietaryÂ is a lie. Â It paints an incorrect & negative picture over all the wonderful things Macromedia/Adobe have done in open source around their products.
Lie #2: “HTML5 being adopted by Google”
Google created the first browser to fully integrate plugins, and continues to work with Adobe to do so. Â Google also utilizes Flash Player in Gmail for both file uploading, andÂ configuringÂ your web cam. Â Google utilizes Flash Player in their online maps product for street view. Â Google Finance utilizes Flash Player for a lot of their charts. Â Their video site, YouTube, utilizes Flash Player for their videos.
Google didn’t start out with Flash. Â They started with text, AJAX, and later Flash. Â They’ve done a lot of forays into HTML5, yes, and will continue to do so. Â Saying they are “adopting” it, and only it and not Flash Player, is incorrect.
Lie #3: “…75% of video on the web is in Flash. What they donâ€™t say is that almost all this video is also available in a more modern format, H.264, and viewable on iPhones, iPods and iPads…”
Incorrect. Â If a video is H264, that doesn’t mean it can play on the iPhone. Â If you look at the iPhone specs, you’ll see the only support a subset of what H264 offers, specifically 2 major components to quality video: Using a maximum of the Baseline profile, with Simple for higher bitrates/resolutions, as well as 2.5 for maximum (ish) bitrate.
Not all H264 videos conform to these specs. Â YouTube converted a lot of their Spark (Flash 6/7) videos to H264 to support iPhone because there was money to be gained in the large investment. Â Even so, not all YouTube videos work on the iPhone, in part because of the aforementioned reasons. Â There is a reason why when you upload a H264 video to YouTube, they’ll often re-encode it.
I’ve been in web video for 7 years. Â Getting video to work in the browser is the easy part. Â Setting up video encoding farms to support thousands/millions of users is not. Â It’s hard and expensive. Â Not everyone has the resources (read money and time) Google has, and that’s why companies like Brightcove are trying toÂ capitalizeÂ on this problem.
MostÂ importantly, HTML5 currently has no universal DRM solution. Â That is why Flash Player’s RTMPE, and soon HTTP Streaming via Project Zeri, are the de-facto standard today. Â Those who deploy video content they either own or license the rights to will not utilize HTML5 because it cannot be protected. Â There is a reason you rent videos in iTunes using their <strike>ACC</strike> MP4 format vs. straight H264. Â Legally, those videos CANNOT be utilized via HTML5.
Also, Hulu.com and others aren’t using H264, they’re using On2’s VP6.
Lie #4: “users arenâ€™t missing much video.”
Every time a user see’s a blue lego instead of the video they wanted to see, they are missing a video. Â There were so many people seeing the blue lego, including Steve Jobs himself on stage demoing the iPad, that they removed the blue lego as a PR effort to make it seem like there was something wrong with the website itself vs. the iPhone/iPad.
…thankfully, Grant Skinner added it back.
Lie #5: “…Flash has recently added support for H.264…”
Incorrect. Â It’s been there since August of 2007. Â That’s almost 3 years. Â That’s a long time in technology.
Lie #6: “…must be run in software…”
Not entirely correct. Â Apple FINALLY gave Adobe and others access to hardware for desktop systems, which Adobe has recently utilized. Â The #1 criticism for Mac’s & Flash video is lack of hardware acceleration. Â This move by Apple will go a long way to improving video experiences, not just for Flash, for browser based video. Â Meaning, cooler Macs and more battery life.
For mobile, Safari/WebKit is using H264 hardware decoding just fine. Â They just won’t expose it, forcing yet again, Flash to utilize a sub par video experience for iPhone (having to launch a URL to utilize the iPhone’s default video player vs. incorporating the video into the experience).
Lie #7: “…When websites re-encode their videos using H.264, they can offer them without using Flash at all…”
See #3. Â Also, not all Flash video is just a video block on a page. Â Some are immersive experiences, games, or involved in compositing with other objects (alpha channels, easier particle systems, etc). Â HTML5 does not currently support some of these features.
Finally, not all video is pre-recorded and progressive. Â Live and streamed events are currently done using Flash Player and Silverlight. Â Yes, I’ve seen systems that can do live H264 via progressive with only seconds latency over CDN’s, regardless, they aren’t what’s being used en masse today. Â This includes DVR like functionality that both technologies offer, including Adative Streaming capabilities to ensure you can see un-interruptedÂ video regardless of your internet connections’s integrity.
Lie #8: “…Flash was designed for PCs using mice, not for touch screens using fingers…”
Incorrect. Â The whole reason Flash Player has continued to stay ahead of the curve is because Macromedia/Adobe innovates it. Â There are gesture & touch API’s in the Flash Player; I and many others have used them for the iPhone resulting in a 100+ apps on the App Store.
Lie #9: “For example, many Flash websites rely on â€œrolloversâ€, which pop up menus or other elements when the mouse arrow hovers over a specific spot.”
Incorrect. Â This was already discounted 2 months ago by Mike Chambers. Â Additionally, I tested both MouseEvent.CLICK, MouseEvent.MOUSE_DOWN, and MouseEvent.ROLL_OVER, and all 3 worked just fine on my iPhone. Â Additionally, I’ve seen video of a Nexus One using the native Flash Player 10.1 that plays a Flex website I made just fine with no code changes to support touch.
Lie #10: “Appleâ€™s revolutionary multi-touch interface doesnâ€™t use a mouse, and there is no concept of a rollover.”
Incorrect. Â There are roll over states for buttons on the iPhone/iPad because you can click/touch on something, which shows the roll over state, but then drag off to not trigger the up, thusÂ cancelingÂ your button click if you didn’t meant to touch something. Â Works the exact same way as a mouse does.
Lie #11: “Most Flash websites will need to be rewritten to support touch-based devices.”
Incorrect, see Mike Chambers’ post in #9.
If both wish to utilize Gesture or Touch events, then BOTH need to re-write/adjust their content to support these events.
Lie #13: “The avalanche of media outlets offering their content for Appleâ€™s mobile devices demonstrates that Flash is no longer necessary to watch video or consume any kind of web content.”
Incorrect. Â See #3. Â Media companies will have to create players like Netflix did to support those devices; these aren’t HTML5, they’re Cocoa.
Half-Truth #1: “Adobe was the last major third party developer to fully adopt Mac OS X.”
iTunes, flagship Apple software product enabling the success of the iPod, selling over 1 billion songs, and empowering digital movie rentals, isn’t Cocoa.
What really matters are features and user experience, not the developer technologies used to make them.
I agree with everything else the article says. Â While the spin is HTML5 is better than Flash, Apple wants you developing with Cocoa, not HTML5; that’s where the money and good user experiences are. Â While many have said that the PR person responsible for writing that article is doing Apple a disservice, I disagree. Â Yes, they do loseÂ creditabilityÂ writing that many lies, and yes, this just fuels the fire for many developers, not just Flash Devs, to focus on Android instead of iPhone.
However, iPhones and iPads still rock. Â While Apple is “only the 10th” largest phone manufacturer, they are the only mobile platform people care about right now in the USA (unless you’re a pissed off Flash/Flex Dev). Â Their app store, combined with the user experience, is un-matched.
Me? Â I’m still trying to learn Cocoa so I too can participate in building applications for these wonderful devices; devices whose sales won’t be hurt by that article. Â My colleagues in the industry? Â Most are heading towards Android along with Adobe. Â Those moonlighting in Flash & iPhone development simultaneously don’t say much, beyond correcting & helping me with my Objective C knowledge on Twitter (y’all rock!).
…oh yeah, and someone cast Cure 2 on Adobe.