The real question is whether developers hate Adobe/Flash/proprietary standards enough to keep promoting HTML5. I think they do for now, but unless someone comes out with a Flash-esque development environment soon, the fervor will eventually die out and people will settle for the path of least resistance, which is Flash.
Flash IDE has the bullet points, but TextMate/Vim/whatever can actually edit code. That is, there exist specialized workflows to solve problems Flash IDE is trying to solve, and they work better.
Adobe documentation is integrated into the IDE, but HTML5 documentation is far and wide abundant (and in my experience actually accurate and intelligible most of the time).
It's easy to whip up a quick project with Flash. But most of the life of software projects is spent in debugging and support. Good luck with that. At the same time, browser tech will enjoy Firebug/Inspector/SpeedTracer, and specialized asset creation workflows, in many cases leading to a more professional looking (and working) result.
And yes, Adobe would do themselves good by getting on with browser tech tools, while they still have the chance.
This one-sided story is getting old.
Using a third-party compiler, debugger and asset management tools helps a ton, but does not validate the technology. Widespread use does.
Shame there is no remedy for Adobe's documentation.
Flash is a great technology. HTML5+JS is a great technology.
Adobe/Macromedia can be, at times, hack-y. Doesn't mean that they didn't manage to have a great idea or 2.
This whole single-minded circle jerk re: HTML5+JS is causing a diffuse in logic and making people "gang" stupid.
It supports memory profiling, debugging, Eclipse plugins etc. We've built our application in it using an MVC style of programming similar to Rails.
The AS editor built into Flash should not be used for more than a screenful of code.
daeken was saying if it is superior, then developers still have that option. They aren't choosing one or the other, as (say) Apple has with not supporting Flash at all on the iPhone/iPad platform. It's good news for everybody except the small contingent that specifically wants Flash to die out. It doesn't hurt people who choose HTML5 for other reasons (such as reaching iPhone users).
Flash comes with a nice, integrated IDE that allows
quick production of visuals and scripting. I think
it'd be hard to make an argument that HTML5 development
is equally assisted for most use cases.
It's not hard at all. I can write my HTML with any editor I like. I can see the source of any page I like. No need to buy Adobe tools or hunt for .fla.Making complex animations (not a sliding nav, for example) is not easy in HTML5+JS. Sorry, it isn't. We can have this argument forever, have yet to see someone produce the evidence of their accusations.
Flash IDE, with all of it's flaws, trumps any "HTML editor" for animation or UX complexity. Sorry, that's just the way it is. No "Visual jQuery" exists.
I do agree that Flash is used when it is not necessary.
However, on the flip of the same token there are those who would have you believe that you should use JS when Flash is a clearly better choice.
Even if it isn't so hard for a programmer to figure out how to duplicate things in HTML5 canvas, a large reason Flash has been able to spread so widely is because it appeals to designers and other visual producers, and is usable by them without much difficulty. To displace Flash, canvas will need to acquire a development environment that does the same.
For all it's worth, you can create full Flash content with notepad, the official command-line compiler, and if you want graphics, some SVG editor or GIMP or whatever.