4 ms·

I don't think he's laying out the whole flash vs HTML5 argument in that post. He says: If HTML could reliably do everything Flash does that would certainly sav

by barrybe 17y ago

I don't think he's laying out the whole flash vs HTML5 argument in that post. He says: If HTML could reliably do everything Flash does that would certainly save us a lot of effort, but that does not appear to be coming to pass. which is probably referring to how HTML5 does not have: efficient vector-based animation, support for audio mixing, strong tool support and ecosystem for creating interactive content, a pathway to run C code (Alchemy), etc.

inimino 17y ago
efficient vector-based animation SVG in HTML (embedded directly in the DOM, not an <img>) is all but certain to happen; the SVG and HTML working groups just have to agree on the details. Of course SVG in an <img> island is possible already, which is what already more integrated with the browser than Flash. support for audio mixing HTML5 has <audio>, and the rest will come in time, with enhancements to what's there now. tool support Actually, there are already more Web developers than Flash developers, so I'm not sure this argument holds much weight... but you can be sure there are people working on this very issue for the Web platform. If these and similar issues all that Flash has going for it against the Open Web, then Flash is on the way out. In a decade, I expect Flash will be as relevant to the Web as Java applets are today.