bq. Surely you would admit that simply adding a Flash adept developer or a web standards guru to the staff doesn’t mean the agency can support a change in their process or that it’s the type of work they want to do. If the pipeline is based on one of these two, the designers are used to designing for it, the project managers know what to expect, and sales people know how to sell the approach’s benefits to clients, it seems rather counterproductive to hire someone that would be happier working in a different environment.
From a business standpoint, it absolutely makes sense to hire the more “familiar” one, the one who can deliver expected results that everyone is used too. But, in my experience, safety sometimes hinders creativity, innovation, and open-mindedness. It often produces unremarkable results and encourages the staff to strive for mediocrity.
bq. The problem with flash is that on most of my Mac OS X computers its a complete resource hog and causes my browsers to crash
I must disagree. You can publish an empty SWF and run it with virtually no lag on resources. That leads me to believe it’s not the player or the SWF format, but what the SWF contains that causes concern. As I mentioned in the article, the unoptimized development is misinterpreted as a faulty platform. Rather than executing the messenger, let’s teach the writer how to craft her message. That way, everyone wins.