Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>To a large extent, the answer to this question depends on how closely you look at the features. Take video as an example - can HTML5 do what Flash does today? If you mean "can they play video?" then the answer is yes - HTML5 will include a tag, that lets you embed video directly into a page without using a plugin. But if you mean "can they play video for 95% or so of the market with a single codec", then the answer is quite different - today, HTML5 requires at least two codecs to be published (H264 and ogg/theora) to covers something less than 40% of the market.</p> <p>Eventually though, when HTML5 video gets into IE and maybe solves its codec issue (though the codec part doesn't appear very likely right now), what will realistically happen is that content owners will have two ways to distribute video, and they'll choose whichever fits their purpose better. So if you want your video to be accessible to search engines, HTML5 is definitely going to be better than Flash. But if you want features that aren't standardized, like DRM, then the proprietary option is going to cover you better than the standardized one.</p> <p>So I think the answer for the future is that it doesn't really matter whether they "do" the same thing - after all, HTML/AJAX does basically the same things that Flex does, but that doesn't mean nobody uses Flex. The difference is in the tooling support, hooks into other technologies, and in the details of all the non-standardized parts of the feature sets.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload