DIGG IT! The debate over AS1 or AS2 is interesting but in the end its all bytecode. Regardless of what toolset made the swf file, the player will interpret the bytecode instructions(compatible or not). What is important is that the swf meets your requirements for functionality and usability.
Different development approaches have merit but all approaches are not created equally for the problem at hand. Some problems are better solved procedurally, some via objects, some via components, and some via a framework or a pattern. In the end you are trying to solve a problem and the toolset simply provides options towards a particular solution. The argument that there is only one way to solve a problem is ego-driven crap.
Personally, I am very comfortable with AS1 and can solve problems with it easily. Having worked with it for years, I know the ins and outs of shaping solutions with it. When I write a line of code with AS1, I know what will happen at runtime. With AS2, that isn't the case, yet.
AS2 provides compile time tools to allow you to detect subtle errors in development. The additions of Classes, Interfaces, and Type Safety are very powerful if used properly and very destructive if used improperly. Developing with them effectively requires understanding how they impact software at runtime. Unfortunately there are only a handful of developers that understand the runtime perspective of AS2 (most work for MM), although this will change over time.
If you understand what a language does at runtime, you can use it in many unexpected ways to solve problems. Good developers understand the runtime perspective of a language, great developers shape solutions from this understanding.
"I should think you Jedi have more respect for the difference between knowledge and wisdom." -Dex
cheers,
ted ;)
0 Responses to “ A Runtime Perspective ”
Post a Comment