5 ms·
You're complaining about the development environment, which is considered to be better than JS/HTML5 by many people. However, the Flash runtime is the reason p
by bad_user 15y ago
You're complaining about the development environment, which is considered to be better than JS/HTML5 by many people.
However, the Flash runtime is the reason people complain about Flash. It is slow, it leaks memory, it crashes like crazy and has been a second-class citizen on every platform other than Windows since forever.
JS/HTML5 on the other hand is a mess in terms of development tools. But it is getting more and more reliable. And it's a real standard with multiple implementations that are extremely competitive. Apple was right for excluding Flash from their mobile browser, as for mobile phones HTML5 is currently much better, even though the technology powering it is newer than Flash.
Adobe's current plans are to build development tools for HTML5/JS too. They are even pushing for improvements in the standard, like CSS3 Regions.
- joeyespo 15y agoWhile these things are true, developing in the Flash environment was a lot of fun and very gratifying. I believe if the Flash development environment was available for JS/HTML5 today, Flash hackers would be much more excited about it. It's not the fact that Flash is going away that causes sadness. Rather, it's the gap between that and having an equally powerful environment for JS/HTML5.
- bad_user 15y agoWell that was partly my point. Another thing I forgot to mention ... Adobe already has an AS3 to Javascript compiler that produces Google Closure compliant code (or this is the plan anyway) and they are using it internally for their own projects.
- discreteevent 15y agoWhat would the differences be between what that compiler does and what the Dart compiler claims it will do when its finished?
- ender7 15y agoSadly, the development environment matters quite a bit. - I will miss being able to declare classes using a sane syntax (Coffeescript helps in this regard) - I will miss the optional type annotations, which caught many a bug for me (you can use JSDoc annotations + closure compiler, but only if you like placing a verbose comment in front of every single variable declaration) - I will miss having an IDE that can actually do code completion (this not possible without type annotations, so it's not coming to Javascript any time soon) - I will miss interfaces - I will miss namespaces (there are various ways to hack namespaces into Javascript. They are all letdowns.) - I will miss color transform filters, drop shadow filters, and blur filters (might become part of CSS if Adobe's proposal gets approval) - I will miss the (mostly excellent) API documentation (MDN tries its best, but is not even close) - I will miss masks (of any arbitrary shape) - I will miss being able to create and dispatch my own events without having to use someone else's event framework - I will miss having all my resources compiled into one blob and loaded together, rather than having to worry about preloading all of my UI images - But most of all, I will miss performance. Yeah, Flash is buggy/slow/memory hog blahblahblahblah. But have you tried doing anything graphically complex in HTML5? Holy shit, your processor will scream. Things that Flash used to laugh at will bring Chrome to its knees. Don't get me started with IE. So no, Flash is not great. It has a ton of warts. But HTML5 is not ready. Not even close. So we're going to have to spend the next ~2-3 years in techno limbo while it catches up. And that makes me sad. HTML5 is particularly not ready on mobile. For example...don't use gradients, since they kill performance. Oh, and don't use opacity either, since that also kills performance. Seriously? I need to build a UI that doesn't use opacity animations? FFFfffuuuu-- Apologies for sounding like a grumpy old man, but promises of "someone will come and fix it with a standard...at some point" don't really get me excited. I worry that in vilifying all the things that Flash did wrong, the web world is going to ignore all the things it did right, and refuse to integrate those things into HTML.
- kamcknig 15y agoBy the time a standard comes along anyway, we'll already be on HTML8 without a standard for it. HTML will never have a standard, and it will never be at a point where all browser implement all the same features.
- luriel 15y agoFlash has had chronic performance and reliability issues even on Windows. And you forgot to mention one of the main issues with Flash: security (or the lack of thereof), it has had so many holes it is starting to make Active X look good (hyperbole, I know, but not by much).
- 9999 15y agoFlash on IE is Active X.