News for hackers. Stuff that matters.
Re:What's new in Flash 11 by whatever_dude on Wednesday September 21, 2011 @07:41PM (#3024161)
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 you'd see a lot in trying to revert that situation. Forcing a maximum tick rate of 60hz (was 120), dropping memory use and performance (tick rate goes to 2hz when hidden on a separate tab, or out of the screen); coming up with new browser APIs so the browse can control the plugin performance; and on and on.

They do deprecate a lot over the years. However, is "eliminated" something people really want? The platform prides itself in the fact that SWFs that worked for Flash 2 still work today, despite the changes in the language and virtual machine. So unless it's a change of security policy, nothing breaks or is "eliminated"; as a developer, I find this to be a good thing as I don't have to have a client coming to me after 6 months complaining about something not working anymore.

Flash is a platform that allows people to do a lot. Including shitty binaries. And there's not much defense against it.

And personally I still have my browsers crash more because of shitty HTML/JS than Flash. YMMV.

Re:What's new in Flash 11 by ed on Wednesday September 21, 2011 @08:25PM (#3024266)
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 else.

What really disappoints me is Adobe's reluctance to support really neat Labs projects like Alchemy. Want to run C (or any language which compiles to C, like haskell!) in the browser? It's been possible since Flash 9, way before NaCl. Official support is coming soon but it's a bit too bad it took so long.

Re:What's new in Flash 11 by Peaker on Wednesday September 21, 2011 @08:38PM (#3024291)
Haskell doesn't really compile to C, unfortunately.

The (deprecated) via-c backend of GHC compiled to something that looked like C, but depended on a horrible Perl script to post-process the object output.

It does have an LLVM backend these days, though, maybe that can work?

Re:What's new in Flash 11 by magicalhobo on Thursday September 22, 2011 @06:04AM (#3025501)
"What really disappoints me is Adobe's reluctance to support really neat Labs projects like Alchemy."

I can't tell if you're saying you know or not, but Alchemy is becoming an official product:

http://blogs.adobe.com/flashplayer/2011/09/updates-from-the-...

Re:What's new in Flash 11 by MetaMan on Wednesday September 21, 2011 @08:45PM (#3024306)
"Crashing in a managed environment is never the developer's fault" !!!

WHAT? Are you serious? Please educate us as to how that is done.

Re:What's new in Flash 11 by georgemcbay on Wednesday September 21, 2011 @09:17PM (#3024401)
He's right though it depends what you mean by a "crash".

An unhandled exception due to referencing a null object that caused the Flash app to crash? Developer's fault, not Adobe's.

A crash that brings down the entire Flash runtime (and possibly the browser hosting it)? Adobe(or the browser vendor)'s fault, not the developers.

Even if the developer does something horribly stupid in ActionScript, the runtime should never die due to developer error.

Re:What's new in Flash 11 by MetaMan on Wednesday September 21, 2011 @09:54PM (#3024498)
Agreed. But most of the crashes I see are of the former type (I.e developers fault).

I honestly can't remember ever seeing a Flash crash actually bring down the the browser. Maybe I've been very lucky.

I see that I'm getting down voted for calling 'ED' out on his sweeping statement where he did not define what he meant by a "crash". Note that for many users a "crash" is when what ever App/game/web-page they are running stops with some error and they can't continue. My basic point is that many (most??) of these, in my experience, are down to developer error.

Many developers seem to have an irrational "hate-fest" going against Flash. For sure there's a lot wrong with it but, for me, all to often "its not the tool but the craftsman at fault".

Re:What's new in Flash 11 by comex on Thursday September 22, 2011 @04:41AM (#3025354)
People are definitely referring to Flash taking down the browser (or crashing the plugin in Chrome and Safari, which have plugin sandboxes). Personally, I've seen "Plug-in Failure" several times even though I rarely visit sites that feature Flash. Steve Jobs wrote that "we know first hand that Flash is the number one reason Macs crash."
Re:What's new in Flash 11 by jessicarios on Thursday September 22, 2011 @07:37AM (#3025678)
It isn't irrational. It's quite simply that my laptop fans run loudly when I'm using flash, draining the battery while not using flash doesn't run my fans or drain my battery. It's a pretty simply complaint. Flash is a power and resource hog for very little upside.
Re:What's new in Flash 11 by ed on Wednesday September 21, 2011 @08:56PM (#3024337)
How can you fault a managed system? Addresses are a few abstractions below the developer.
Re:What's new in Flash 11 by MetaMan on Wednesday September 21, 2011 @09:12PM (#3024384)
For me there are many real world cases which can't be handled without showing the user a fatal error.

E.g. - the developer asks for an runtime created asset that doesn't exist anymore or there's a condition under which a block of code runs forever (actually in this case the flash runtime stops after 15 seconds of activity and allows the user to kill it but it's still a "crash" insofar as the user is concerned.

Re:What's new in Flash 11 by beagle3 on Wednesday September 21, 2011 @10:17PM (#3024566)
But Flash often crashes way worse than that; it segfaults, or raises a structured exception. It used to take browser processes with it, before Chrome made it popular to have plugins in their own process.

I suspect Flash's (lack of) stability was one of the reasons for considering this design decision in Chrome.

Re:What's new in Flash 11 by ary on Wednesday September 21, 2011 @09:24PM (#3024420)
Because the whole point of it being managed is that you can't crash it, and if you can it's a bug.
Re:What's new in Flash 11 by ewrgsdfg on Thursday September 22, 2011 @12:25AM (#3024845)
Agreed.