Now open is another issue...
Where is the "not open" you guys claim? Flex SDK + Eclipse == free Flash development.
I swear HTML5 fanatics just make stuff up these days. You'll use Windows, Flickr, Google, and Hacker News - all privately owned systems. But god forbid Flash is bad because... why?
Lack of openness: a browser plugin that is less stable and slower on Mac and Linux that noone else can fix except Adobe...and only if they choose to do so.
Lack of openness: a browser plugin that doesn't properly utilize cookies on non-IE browsers that noone else can fix except Adobe...and only if they choose to do so.
Lack of openness: a browser plugin that doesn't properly return HTTP status codes on OS X that noone else can fix except Adobe...and only if they choose to do so.
The SWF standards (and associated standards like RTMP) are available for free on the Adobe website. You are permitted to construct alternative implementations based on this specification. I think it meets the definition of an open standard.
Would HTML not be an open standard if the only browser we had was IE, and it was horribly buggy? No - the quality of the available implementations is irrelevant to a standards "openness".
Sure there's CPU problems and there will always be more-optimized forms of code. But Flash has a timeline, which is something few here will understand or appreciate.
Plus it really is ubiquitous, unlike anything else. I'll take a small performance hit if it means I don't have to learn/write/test multiple languages and systems.
I'm not in this for the code. I'm in it for the UX.
CMS systems already solve the problem of "how do I make and update a website", with an order of magnitude less hassle for the developer, and much less hassle for the user.
Adobe on the other hand has built industry standard tools over and over again (Photoshop, Illustrator, etc). They've proven that they can export their apps to other platforms (iPhone). What they're not so good at is building open browser runtimes...