Adobe's Flash tools now embrace HTML 5. Sadly Flash is still alive Adobe’s long road to open standards has been freshly re-paved with an HTML5-friendly suite of tools. The firm recently announced Animate CC as its “premier” web animation tool for developing HTML5. In its previous incarnation, Animate CC had been called Flash Professional CC – being built for the firm’s once flagship, and …
I know its the standard groupthink to knock flash, and yes it has had more than its fair share of bugs and exploits. OTOH I'd like to see you try and write a fully portable and programmable HD video codec and animation system with network support and hardware acceleration and make it bug free.
The thing that makes me really laugh however, is that the same people who are constantly kicking flash seem to believe that somehow miraculously the javascript interpreter and video codecs required for HTML5 will be exploit free. If (or when) HTML5 ever achieves the same functionality as Flash and the same ease of coding without having to serve up the standard issue rats nest of jerry rigged code and markup that is the sorry mess that we put up with in web pages today AND its not exploitable in any way then maybe I'll take notice.
I think it's more the case that: (i) Flash massively overreached on features, going a long way beyond animation and video, and managed only relatively poor hardware acceleration, especially away from Windows; and (ii) such exploits in HTML5 delivery code as will be found will likely be limited to specific combinations of browser and OS. So they'll be smaller in scope and therefore easier to avoid.
Its death is also appealing because it eliminates redundancy — why should my browser have two separate scripting engines, one for JavaScript and one for a weird proprietary off-shoot of JavaScript? — and given that all the major OS vendors (Microsoft, Apple, Google) provide a browser, it puts the people who expose the available hardware acceleration and who debug the OS under the same umbrella as some of the people responsible for an implementation the web standards. We shouldn't again go through "Apple doesn't expose the hardware acceleration" "Yes we do, you don't use it" "That's because you expose it in a stupid fashion", etc, or "A third of reported crashes on the Mac are Flash" "Oh, well, Macs must be broken then". Which are both Apple examples but, you know, cuts to the point that a centralised, single-vendor implementation of an essential standard is undesirable in a world of diverse clients.
"A third of reported crashes on the Mac are Flash" "Oh, well, Macs must be broken then".
There is NO excuse for a browser crashing because of a screwed up flash plugin. It should be run as an entirely seperate child process in the unix fashion, not as a seperate thread in the windows fashion which can corrupt the parent thread. If a child process crashes you mop up the mess and try again, if a thread crashes it'll usually take every other thread down with it. Only piss poor programmers will use a thread instead of a process for a supposedly sandboxed plugin.
I would think that they'd just use standard animation software to make their cartoons like a real animator would.
Using something like Flash for animation is like trying to nail two boards together by setting a nail on the floor point-up and then slamming the two pieces of wood down on to it.
You say "Adobe is also doing its best to ensure the continued use of Flash on the new web. Flash dominated on PCs as a medium for serving media and ads."
Who's right, I wished flash would just curl up and die either way
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
