What's new in Flash 11

Post by carussell » Thu, Sep 22, 2011, 8:52 AM UTC

acqq wrote: post #60

Note: "High-efficiency SWF compression support: Developers can now take advantage of LZMA compression for their SWF files. LZMA compression can reduce SWF size by up to 40 percent, enabling users to benefit from richer experiences with shorter download times and reduced bandwidth consumption." If I understand correctly, they must have used the code developed by Igor Pavlov, the author of 7z, who made it LGPL. LGPL me…

  LICENSE
  -------
  
  7z ANSI-C Decoder is part of the LZMA SDK.
  LZMA SDK is written and placed in the public domain by Igor Pavlov.

Post by gtdminh » Thu, Sep 22, 2011, 9:22 AM UTC

ender7 wrote: post #30

Some of these are really welcome changes for me (native JSON, bezier curves, TLS sockets, DisplayObjectContainer.removeChildren). And yet... And yet I'm still planning on switching my web app to HTML5. This is coming from a guy who's sunk over two years of development into Flash. It's not because the runtime is buggy and/or crashy (it is, but it's not that bad). It's not because it's so much easier to develop in HTML…

Post by magicalhobo » Thu, Sep 22, 2011, 10:04 AM UTC

ed wrote: post #19

whatever_dude wrote: post #6

Earlier quoted context omitted.

I'd disagree. I've come to realize that crashing is usually either the developer's fault (e.g. trying to do something that doesn't make sense) or the browser's (with Firefox I'd get crashes constantly, since their sandboxing actually breaks the plugin more often than it protects from it; with Chrome, using the same version of the plugin, I get none). Still, if you look at what they've done in the past couple of years…

Crashing in a managed environment like Flash is never the developer's fault. These issues are either introduced by the browser vendor or Adobe. It's worth noting that Adobe is very reluctant to deprecate API's. They've historically preferred (with AVM1/AVM2) bundling new VM's into the player over deprecating features. And any deprecation must be version-specific, and tends to be more for API consistency than anything…

Post by jessicarios » Thu, Sep 22, 2011, 11:35 AM UTC

ido wrote: post #54

ender7 wrote: post #30

Some of these are really welcome changes for me (native JSON, bezier curves, TLS sockets, DisplayObjectContainer.removeChildren). And yet... And yet I'm still planning on switching my web app to HTML5. This is coming from a guy who's sunk over two years of development into Flash. It's not because the runtime is buggy and/or crashy (it is, but it's not that bad). It's not because it's so much easier to develop in HTML…

I was originally in your shoes, but after my first real attempt at writing a game in js/html I came to the conclusion it's still a ton easier in flash. If you are talking about something more static (e.g. a non-game application or a fairly static game like a match-3) it's probably less of an issue.

Post by jessicarios » Thu, Sep 22, 2011, 11:39 AM UTC

Fizzer wrote: post #20

davidu wrote: post #2

I guess crashing isn't a feature. I'm not trying to be a troll, but let's be honest -- There has never been a version of Flash that hasn't piece a complete piece of garbage when it comes to stability and performance. If Adobe "got it" this list of "What's new" would include words like "removed" and "deprecated" and "eliminated." Those words don't appear once. They've just thrown more stuff into the kitchen sink that…

My experience doesn't match your statements at all. I run a Flash website (it's a game), and Flash is pretty much rock solid for me. My site has been up over 3 years, has over 80k lines of Actionscript, and I can count the number of times I've seen Flash crash on one hand. Even if you include reports from my users who have Flash crash on them, the number is less than 20. That's probably not too far from any software…