nascentone
Plus not having the structure as part of the standard will make iterative development a nightmare. Instead of being reliant on a proprietary runtime (like Flash Player) we are reliant on proprietary compilers and libraries. How is that better?
Standards do not. If you think it does, I would predict you aren't a designer, because there's a big difference between technical parity and realistic results.
I can concede that as a designer, I really don't care if HTML is technically better for some reason, I just want to have the freedom to do cool stuff, and that this is the tension between those are "Flash fanboys" and those who are Standards fanboys.
And the thing that amazes me is the fact that when it comes to longevity, Flash has nothing to apologize for. I can view Flash 3 SWFs and they look exactly how I made them. HTML sites break and blow up in spectacular fashion within months sometimes. A new browser comes out and now your beautiful website looks like trash because something isn't rendered the same. Not always, but more often than I want to deal with (which would be never), and I never once had that problem with Flash.
I just wish you could do your thing, and I could do mine. Well, congrats, you win.
Exactly. And this is why Flash was so awesome.
Standards are the opposite side of the spectrum, full of the most pedantic and hyper-technical people, and it's why I hate standards. Just standardize everything in Flash and I'd be happy.
As an artist, you're right, I hated going from AS2 to AS3 but once I got past the challenge (rather quickly) I loved it. I'd like to have your enthusiasm, but going from Flash to standards doesn't look the same: I hated going from AS2 to AS3 because it made some things more strict, but it paid off because the resulting product was better. Going from Flash to HTML, however, is the opposite -- things are incredibly messy in JS, and as a result, stuff breaks and is inconsistent and buggy all over the place. This, to an artist, is soul crushing. I want to make cool stuff, and I will climb any mountain to do so, but once I do I don't want to see my work just crumble to bits because I switched to a different machine/device/screen.
I'm not just hoping I'm counting on Adobe or someone delivering a good Javascript IDE that mimics OOP design, and I'm keeping an eye on Google's Dart project, but even after that I'm not expecting the experience to be nearly as smooth or creatively liberating as Flash.
I know Javascript, your comment suggests you don't know ActionScript's history: AS1 was an ECMASscript language just like JS, so to that end it was actually literally the same language as JS running in a different environment with a different API. The latest iteration of JS has hardly changed since then, whereas AS1 evolved into AS2 then AS3, which is now a much more advanced OOP language, and it's still evolving. Going from AS3 to JS is literally like going backwards in time.
This is what's depressing, though. I want to make awesome things, but HTML is simply an inferior and more restrictive platform than Flash. The thought of programming in Javascript instead of ActionScript 3 is soul-crushing. Javascript is basically ActionScript 1.0 (which I thought I migrated from years ago) without the cross browser consistency and more advanced graphical APIs.
Long live the internet, but losing Flash is a bad thing for the internet. It's not Flash that needs to die, it's the entire archaic and poor sighted standards stack (HTML/CSS/Javascript and the horrible plain file HTTP delivery system) in favor of a new standard stack that can actually do something close to the Flash Player.