Is it just me or have there been a lot of blog posts lately in response to Grant Skinner's post about the memory leak in Flash Player? Now I don't mean to say that, this isn't a problem. But posts like this or this are a bit over the top. The problem doesn't mean that applications can't be built with AIR or Flex. Grant Skinner's description describes the problem pretty accurately which to me sounds like they would never affect many applications.
In the first link above, Jim Robson title's his post "Time to switch to Ajax?" which I find a little humorous since Internet Explorer has some serious memory issues of its own which make AJAX apps just a susceptible to memory issues.
I, like everyone else, hope that Adobe makes this problem easier to deal with, but I don't think we should all run for cover just yet.
2 comments:
I have to agree. I was surprised at some of the comments too.
Rob,
My post concludes with the statement that I'm *not* ready to throw in the towel as yet. I still think Flash and Flex beat Ajax.
In fact, if you read my post on the Canvas element, you'll get a better idea of how I feel about relying on JavaScript: http://www.robsondesign.com/blog/index.php/category/canvas/
However, there is a very serious consideration that you're not addressing: If the Flash player doesn't continue to maintain the level of backward compatibility that it has until now, then Flash does lose one of its great advantages over Ajax. And, if browsers really do become standards-compliant, then the "no plug-ins" crowd gains some serious ground, because the browser idiosyncrasies become a non-issue.
Anyway, thanks for the feedback. In the future, feel free to post comments right in my blog; I'll be happy to hear from you!
- Jim
Post a Comment