1 files changed, 48 insertions, 0 deletions
diff --git a/wired/old/published/html5flash.txt b/wired/old/published/html5flash.txt
new file mode 100644
index 0000000..c7e8d1c
--- /dev/null
+++ b/wired/old/published/html5flash.txt
@@ -0,0 +1,48 @@
+Adobe's Flash plugin, the source of much rich media, audio, video and animation on the web, has taken a beating in recent years. First the iPhone ignored it. Then Google announced a (beta) version of YouTube that uses HTML5's new video tags instead of Flash. Other video sites have announced similar programs it looks as though Flash's days are numbered.
+
+One of the goals of HTML5 is make sure that the web has built-in tools that don't rely on vender specific plugins like Flash. Thanks to HTML5 support in modern browsers, publishers no longer need to turn to Flash to display rich media, video or animations. HTML5 offers both audio and video tags, was well as the new canvas tag for animation. 
+
+Most modern browsers already support these new elements and some are also stepping up their SVG support, giving developers another way to animate. Yet we're a long way from a Flash-free web. The main YouTube site still uses Flash and anyone with an iPhone or iPad can tell you how annoying it is to see the broken plugin icon where Flash content should be.
+
+So what will it take for HTML5 and its newfound capabilities to truly supplant Flash?
+
+There are three main areas where Flash is the dominate tool on the web: video, audio and animation. To truly supplant Flash, web browsers will need to improve their HTML5 support, publishers need to begin publishing their content in HTML5 native code by default.
+
+TK quote
+
+###Video
+
+By far the furthest along, HTML5 video is well on its way to supplanting Flash as the dominate means of embedding video on the web. However, there is a major stumbling block -- video codecs.
+
+In order for your browser to display video natively using the HTML5 video tag the browser needs to know which codec to use to decode and play the video. Because the W3C, the web's governing standards body, declined to specify a standard video codec to go along with new video element, the choice of codecs to support lies with each web browser.
+
+Browser manufacturers are split into two camps, those that support the free, open Ogg Theora codec (Chrome, Firefox and Opera) and those that support the proprietary H.264 codec (Chrome, IE9, Safari and Safari Mobile). 
+
+If HTML5 is going to truly supplant Flash, either browsers need to pick a single codec or publishers need to publish video in multiple codecs.
+
+At the moment, YouTube's HTML5 video support is limited to web browsers that support the H.264 video codec -- namely Google's Chrome and Apple's Safari and Mobile Safari. That means Firefox and Opera won't work. One solution would be for YouTube and others to offer a second video encoded in OGG format, however, the other solution would be to simply fall back to Flash.
+
+Unfortunately, because Flash can already play H.264 video, the code to fall back straight from HTML5 video to Flash is significantly less effort than re-encoding the millions of videos on YouTube. 
+
+At least for now browsers remain divided and most publishers are opting to use one or the other (Wikipedia only publishes OGG), falling back to Flash for browsers that don't use the other, which means Flash video isn't going anywhere any time soon.
+
+
+
+But the pace of the web is far faster than standards bodies are equipped to deal with. As CSS 2 began to catch on Flash shifted from something used to create whole sites, to something that filled the gaps in HTML, namely video players, interactive charts and graphs and animation.
+
+Now standards are once again catching up with the web and Flash's current niches can now be filled without Flash.
+
+The main problem with Flash in the eyes of its detractors is that it isn't a free and open technology. While roughly 70 percent of the Flash stack -- from elements of the player to the tools use to build Flash files -- have been released as open source, it is still at the end of the day, a technology produced and largely controlled by a single entity -- Adobe.
+
+But just as Flash filled niches that standards couldn't fill, even with the new standards, Flash will still likely have a role on the web for some time.
+
+Things HTML5 can't do: 
+
+
+
+3) SVG and animation
+
+
+4) Flash innovations that HTML5 can't compete with 
+    - the new RTMFP protocol for decentralized chat apps, web conferences, P2P radio, possible voip in the browser, etc.
+    - the slow speed of standards development vs the fairly fast speed or Adobe 
+\ No newline at end of file