PS：我也持这种观点，FLASH就是FLASH，我们没必要也不应该总把它往其它的东西上靠。
原文地址：
http://www.actionscript.com/archives/00000560.html
Given how much of a cult phenomenon Flash has become, it amazes me that we as developers continuously disguise it as something else.
We all know that Flash has a total cult following. I think it抯 the only software/platform/programming language that people name their firstborns after and whose beta people would be willing to pay money to be a part of. (I抦 just guessing here, but come on, you know you would.) So why do we have such a hard time letting Flash be Flash? We are constantly using Flash in ways that emulate other standards. One example is the browser. We want Flash do be able to do the same things that HTML-based pages in the browser can do. We want ALINK and VLINK, status messages, and use of the back button. We bend over backwards in order to make Flash do the things that HTML does. We even create components that think they抮e HTML tables.
Another thing we like to do is imitate the look of our operating systems. We create scrollbars that look just like the Windows scrollbar, and popup menus that are very reminiscent of Mac OS X UI widgets. And now that Flash is turning into more of an application development tool, programmers are trying to copycat Java. We want the Flash programming environment to behave just like Java, the more similar the better. We want strict typing, version control and a class browser. If Flash doesn抰 behave enough like Java natively, we will find ways to make it. Let抯 save all of our classes as separate files and just pretend that we抮e actually compiling them.
But Flash is Flash. It抯 not HTML or Java or Aqua. Why all this mimicry? If we love Flash so much, why can抰 we let it be itself? The most seemly answer lies in usability. We want to offer people interfaces that they are familiar with and feel comfortable using. We don抰 want to confuse them with obfuscated navigation anymore. We have been there, done that. Now it抯 all about standardization.
The reason we seek standardization and rules is that Flash is a blank canvas. It抯 not just a blank canvas in the way Freehand is. It not only gives you control over the design of a simple header graphic like Freehand does, but the freedom to design an entire application from scratch without any boundaries. You don抰 HAVE to use cookie-cutter interface elements like you do in Java. Instead, you can build your own interface and make it look... like Flash.
But what does Flash look like? Flash has never had a very consistent appearance. The Halo look might change that. The Halo look might be the future face of Flash, and it抯 different from HTML or Java or our OS. But even so, it抯 still a canned look. It sets up rules for what Flash should look like. I don抰 like rules. Similarly, as we move more towards object-oriented programming, we start establishing even more rules and become less forgiving and less flexible in our coding styles. It抯 starting to make me feel a little claustrophobic.
But the great thing about Flash is that you don抰 have to follow any of the rules. You can choose to, but you don抰 have to. You don抰 have to emulate something that it抯 really not. It can be anything you want it to be. Do you want to play by the rules or do you want to let Flash be Flash?
The choice is yours. Let抯 keep it that way.
