Great article:
http://www.roughlydrafted.com/2010/03/11/f...-web-standards/
QUOTE
What Ozer should do instead is present the plain truth that Flash is a terrible platform for creating web content because it violates everything the web was designed to do: openly share content using openly documented specifications that any vendor can implement in competitive ways that advance the state of the art in hyperlinked, multimedia communications. Flash smothers the web with closed binaries that require Adobe’s interest to play back.
More about why Flash won't really work on iPhone, iPod and iPad... the multi-touch UI that Apple enforces.
http://www.roughlydrafted.com/2010/02/20/a...cant-use-flash/
An older article:
QUOTE
lavalight Says:
Tue, Jun 17, 08 at 10:03 PM
People are missing the point of the article, I think. The point is not “technical challenges” that can eventually be overcome, the point is Apple is taking steps to establish multi-touch as the true and rightful successor to the mouse-and-desktop interface.
For that to occur, Apple is strategically preventing anything that had the potential to break the multi-touch experience. You CANNOT rely on Adobe or any other developer to avoid the scenario of having double-tap launch on app for some apps while it zooms in other apps. Double tap ALWAYS needs to be zoom and Flash on iphone would by default break this because Flash developers are going to develop from a WIMP frame of mind.
By enforcing the use of Apple-only APIs, Apple ensures multi-touch is not only pristine, but practical. Flash has absolutely no value in establishing the multi-touch paradigm – in fact, it’s highly detrimental. For this reason ALONE, Flash will never be on iPhone.
Adobe and pro-Flash pundits are like amateur chess players trying to convince the world they can win a chess match if they only capturing the other guy’s Queen with their Bishop NOW. Apple is Kasparov thinking 10 moves ahead and systematically taking apart the other side, piece by piece, unperturbed by all the commotion of spectators.
Which is to say, Apple is not trapped by the dogma of established thinking.
http://counternotions.com/2008/06/17/flash-iphone/
Kind of reminds me of a phrase in a song... about "all those relatives we've been avoiding all those years!"

Got any of those?!!!

I do remember a Cold War joke: A visitor to Czechoslovakia asked one of the residents whether he regarded the Russians as family or friends. "Family, of course..... After all, you can choose your friends....." 
Anyway the thought is about "all those relatives we've been avoiding all those years!"

Got any of those?!!!

Apparently I have 5 of them. 
I do remember a Cold War joke: A visitor to Czechoslovakia asked one of the residents whether he regarded the Russians as family or friends. "Family, of course..... After all, you can choose your friends....."

HAHAHAHAHA!!!!!!
It annoys me no end that way too many people use Flash for completely spurious reasons. The silliest site I've seen yet is this one:
http://www.patinagroup.com/home.phpThe Flash is used for TEXT - simply because they wanted to use fonts that aren't "web safe" (ie: on every Mac or PC on the planet). It's completely insane - and completely unnecessary.

Too bad, these two guys in charge of the Patina Group are two very big heavy-weights in the industry!
But well, you know, maybe the food has more "Flash" than substance?

Chris
QUOTE
The Flash is used for TEXT - simply because they wanted to use fonts that aren't "web safe" (ie: on every Mac or PC on the planet). It's completely insane - and completely unnecessary.
I've seen that, also and decided to see what and why. I assume that what you are seeing is some version if the Inman Font Replacement method.
I've also been looking for ways to use something besides the ~dozen "web-safe" fonts, mainly for headings and/or drop caps, but without resorting to Flash®. There's a lot of info on using Flash, of course. Others claim javascript is the only way. Some say both technologies are needed to be reliable, usually forgetting that many have both javascript and Flash® turned off/disabled.
I decided to test/play with the few free embedded fonts that are available and use the @font-face CSS property. If there is room on one's server for the usual three different formats needed, and most of your audience is on DSL or better, this seems quit usable. Even Exploder has been able to use this function since version 6. And newer browsers are mostly already CSS3 capable, anyway.
The biggest problems are:1. Finding really good fonts, there are many "free" fonts around, but few meet any kind of quality control or include the extra bits of information to make them suitable for use.
2. Creating the three different file formats needed to support M$, SVG and the rest of the World (known Universe).
The first problem is basically up to the font foundries, although there are now several small font designers that realize the potential of getting one's work seen. 
The second problem has been completely and very conveniently solved by <Font Squirrel> and for free, of course! 
The biggest 'trick' is getting the CSS set up correctly so that Exploder gets 'fed' first, without crashing the browser... Here's a couple of sites that explain and demonstrate how to use this method that claims to support ~97%+ browsers.Explanations/DemonstrationsFree Font Sources