[kreek]

I agree that the majority of the blame for Flash dying is Adobe's fault but not for the reasons you outlined. Outside of security concerns everything bad about Flash can be accomplished with 'HTML5', <canvas>, SVG, and JavaScript if you throw the wrong developer at it.

Adobe's biggest mistake was not open sourcing Flash as HTML5's canvas and audio in one. It could have been rewritten to use JavaScript. Converting a game/app from AS3 to JS on 'Flash Canvas' would have been trivial.

I can live with Flash going away but there's a lot of good we're throwing out with the bath water. ActionScript 3 is a pretty nice language. It's basically a mix of Java or C# and JavaScript (it has events and callbacks but not scope issues). There was no need for an ActionScript the Good Parts book.

HTML5's canvas is very primitive compared to Flash's display list. With the display list you have a hierarchy of visual objects (Sprites) so objects can added as children of other objects and if the child dispatches an event it can bubble all the way up the list to the root parent.

[erichocean]

FWIW, Blossom does that kind of thing for applications (I'm the author).

https://github.com/fohr/blossom

I'll be giving a talk later this month at Throne of JS in Toronto.