Quote:
Originally Posted by TenoBell 
Here is an explanation as to the problem with Flash on the iPhone.
The last thought I had was about the lack of Flash on the handset. Ive done a lot of work with Flash on the desktop lately on Windows and I have to say that despite Adobes efforts to modernize their infrastructure, Flash is still a very primitive technology with strong roots in education CD-ROMs on Mac OS 9 theyve made tremendous strides in terms of rapid application development and deployment, but I dont think performance or reliability has ever really been on Adobes radar with this product.
Some of the problems Ive encountered include random crashes on shutdown, enormous memory leaks in the runtime (a leak in something that draws at 24fps is a huge issue!) not to mention Flashs notoriously awful performance. On the application side, many Flash applications (no naming names) written to run in Flash in a browser just dont care about performance or resource utilization because most web applications have a process lifetime of a page view, or about 10 seconds. Finally, in a mobile context, consider the effect that Flashs inefficient programming model will have on battery life. The last thing to remember is that the Flash runtimes performance is about 4-20x worse on Mac OS X than it is on Windows I bet Apple evaluated its options and decided it didnt want to have its browser experience marred by Adobes lack of focus. You can also bet that with all the crazy user-space scaling tricks that iPhoneSafari does, Flash wouldnt work.
This isnt to say that Flash on the handset wouldnt be useful, but if you consider the use cases its really not as big a deal as you might think.
http://www.stuffonfire.com/2007/06/13/iphone-sdk/

Here is an explanation as to the problem with Flash on the iPhone.
The last thought I had was about the lack of Flash on the handset. Ive done a lot of work with Flash on the desktop lately on Windows and I have to say that despite Adobes efforts to modernize their infrastructure, Flash is still a very primitive technology with strong roots in education CD-ROMs on Mac OS 9 theyve made tremendous strides in terms of rapid application development and deployment, but I dont think performance or reliability has ever really been on Adobes radar with this product.
Some of the problems Ive encountered include random crashes on shutdown, enormous memory leaks in the runtime (a leak in something that draws at 24fps is a huge issue!) not to mention Flashs notoriously awful performance. On the application side, many Flash applications (no naming names) written to run in Flash in a browser just dont care about performance or resource utilization because most web applications have a process lifetime of a page view, or about 10 seconds. Finally, in a mobile context, consider the effect that Flashs inefficient programming model will have on battery life. The last thing to remember is that the Flash runtimes performance is about 4-20x worse on Mac OS X than it is on Windows I bet Apple evaluated its options and decided it didnt want to have its browser experience marred by Adobes lack of focus. You can also bet that with all the crazy user-space scaling tricks that iPhoneSafari does, Flash wouldnt work.
This isnt to say that Flash on the handset wouldnt be useful, but if you consider the use cases its really not as big a deal as you might think.
http://www.stuffonfire.com/2007/06/13/iphone-sdk/
Despite that, flash is still the most important standard on the web for the purpose it has.
Apple could, and should have, solved this problem by buying Macromedia when they put themselves up for sale, instead of letting it go to Adobe.






, Here we have plenty of unpopulated forest with excellent cellular data connections and I guess soon wifi connections as well, if you ever consider change of scenery 




