Browsing articles tagged with " Delivery Mechanism"

Adobe Flash 10.1 The Good, The Better, and The Scary

Jun 10, 2010   //   by David Bates   //   Uncategorized  //  1 Comment

Today Adobe released their new version of the flash player 10.1 and I will say it was a much anticipated update for me. I love flash and have developed in it since it’s early day when it was another product altogether. Flash started out as a way for me to program desktop apps that looked and felt the way I wanted as I have always loved to be able to create the interface and then program it to do what I want. Since then my love of Flash has faded in and out as changes and flaws where found in the system. I almost completely wrote off flash until YouTube and Air had launched. I had been writing projectors for autoplay cd’s for years and air gave me a whole different type of application delivery mechanism. Anyway I love flash and even though I use Silverlight quite a bit, when someone needs a project completed in a hurry and want it to look custom my default is always Flash. So with that here are my thoughts on the release.

The Good:
As you all are aware Apple recently hit Adobe below the belt saying that security flaws and memory errors. I would have expected that in Adobe’s press release they would have addressed that first. But instead they slyly take on the mobile market slating that performance and low power was their main focus. This should make Google happy as it show them that Adobe is not lying down and taking Apple’s low punch lightly.
Better Hardware video decoding… they already own most of the video market. HTML is too early and silver light is just now hitting the market hard. I would have liked to have seen more about HTML 5 video and how Adobe was going to provide tools for video publishing compatible with HTML 5.
Mac Specific Improvements: this is a straight jab at Jobs. I read this as here you go. You wined and we fixed it, now put us in the iPad :)

The Better:
Mulitouch: I have been having to use third party apps to accomplish this thusfar it is great to see this come to the mainstream and is also another sideways jab at Jobs
Multi-Tab memory usage: This is much improved and a much anticipated release. If you have a ton of windows open and multiple flash objects they each have their own memory space. Adobe has streamlined this now.

The Scary:

Ok this one paragraph scared the heck out of me:
“Now, content that runs in Flash Player will automatically shut down when the available memory is running low.”
This is scary because what if you are running a mission critical flash app and you run out of memory? They also did not state whether it was physical RAM or paged? Scary stuff.

Hope you enjoy
David Bates