Some favorite site feeds aggregated locally: iPhone Development RSS   Adobe Labs RSS   Macrumors RSS

Friday, October 24, 2008

Mike Chambers is asking if you're still developing in AS2/AS1

Friday, October 24, 2008   

Mike Chambers has posted a question to the community: are you still developing in AS2/AS1 and if so, why?

There are currently 56 responses to this question, and there are some pretty interesting responses there.

I personally haven't developed or maintained anything written in Actionscript 2 for well over a year, perhaps a while longer. I have not looked back once since. My days have been much less stressful to say the least.

Actionscript 2 for me was kind of like something you loved while you were actually doing it (no alternative), but when you moved past it, it's something you blocked from your memory altogether. I used to pride myself in being someone who knew what the useful and sometimes necessary bizarre timing tricks were, the idiosyncrasies of the AS2 language, the techniques using prototyping, etc. 

I am so glad those days for me have long since past. I forced myself into developing in AS3 and I admit it took a while to get accustomed to. Most of the time I knew what I wanted to do but didn't always know what packages I needed to import to provide the right functionality I was looking for.

With time and failures comes experience. It's the best way to learn as far as I am concerned. You need to beat your head against the wall quite a bit, and that's when your solutions stick with you and grow that bubble.

Go leave your mark at Mike's blog.
 
 Return to the main page
Comments:

There are currently 3 Comments:

Anonymous Anonymous said...
“So you're okay with the bizarre tricks and idiosyncrasies of AS3? Here's one: On one site, after installing the Flash 9.0.3 authoring update, I had to force Mac users to update their browser plug-ins to release 115 because compiling with this update broke all the built-in components when using older FP9 plug-ins.

There's no question AS3 is a vast improvement over AS2, but Adobe QA blew it with AS3 in Flash 9. And what's with all those unresolved bugs for the Flash player in their public bugbase?”
 
Blogger e.dolecki said...
October 25, 2008 11:01 AM
“Could you elaborate on what you mean by built-in components being broken? I know Adobe hold backwards compatibility the Holy Grail of any release, and I have not heard of such a thing happening in regards to components.

What might it have to do with Mac users and the built in components?”
 
Anonymous Anonymous said...
October 25, 2008 5:15 PM
“By "broken" I mean Holy Hand Grenade of Antioch broken -- all the ScrollPanes and ComboBoxes just sat there like useless lumps. I can't find the document, but I later discovered a read me or tech note somewhere which mentioned the problem -- I believe it was related to setting the swf's window mode to transparent. Upgrading to the release 115 plug-in solved the problem for Safari and Firefox Mac users.

This wasn't an issue with PC users having older versions of the Flash 9 plug-in -- I tested all of them. (Thank you, Kewbee :))

Why? You'd have to ask Adobe.

And I was wrong about the update -- it was 9.0.2, not 9.0.3 that caused the problem.

I see they have already released a bug fix for the Flash 10 player, less than two weeks after the initial release. It's good that they're quick to respond to problems (sometimes), but it doesn't exactly inspire confidence in their QA processes.”
 
 Leave a comment