And yet that's exactly what some people try to do. flash reminds me of an Easy Bake Oven (an old children's toy)--it was pretty amazing, and it did bake things. But the problem I see is developers who see a Super Easy Bake Oven, and they try to bake a cake in it. The Oven might have managed a cake, but it would have been very slow (I think the heat source was a light bulb.)
Analogous problems come up with trying to make flash run a user interface, for example. It sort of works, but just barely.
Notable fails:
Adobe Digital Editions--an interesting effort, but you can see its flash underpinings
Geni.com--every time I have to start up a flash app to display or enter data, I think: oh, Lord.
My biggest complaint: slow and mushy. Compare the above two examples to the Chrome browser. All three are doing similar things: assemble and format some data, display it, and wait for user input. But Chrome runs ten to a hundred times faster. Why is that?
tbc
