Originally Posted by mstone
Flash cannot run on iPhone - WRONG Flash 1 can using Gordon.js
If that's "flash" then why is there still a fuss about this?
(that was a rhetorical question - your statment is rediculous since the Gordon.js is hardly "flash" - hence we are all here still talking about it)
Flash is for lazy developers - WRONG Flash is so easy that non-experts can do simple things
I'm not so sure I want to use programs written by non-experts. I'm sure a user focused company like Apple is even less sure that this argument is worthy of consideration. Not all discrimination is bad!
Flash ported iPhone apps have never been available - WRONG several were accepted by Apple
Approval by Apple for an App is not a blanket approval forever. Apple's not de-compiling or reading through source code. It's also clear that Apple was overwhelmed, and is still probably pretty overwhelmed by the success of the App Store. There are plenty of examples of Apple going back and pulling programs for a multitude of reasons (not that I always agree with their reasons).
And before anyone whines about how unfair Apple is, Google has done it too and I thought I saw where Palm has with the WebOS but I couldn't find the reference I was looking for so take it for what you want.
Flash is responsible for Mac crashes - WRONG only Flash programmers cause crashes
If flash is such a crappy environment that poor practices by flash programmers can lock up my browser on a routine basis then.... it's a flash problem! It's so woven into many web sites that it needs to be a heck of a lot more robust than it is now! If you have "non-experts" creating flash apps, then flash had better be able to keep these "non-expert" flash authors from shooting themselves in the foot, and by proxy shooting my computer as well.
At least with Safari 5, I can kill flash in Activity Monitor, regain control of my browser and resume work.
Adobe doesn't care about Mac users - WRONG Adobe sells a lot of pro applications for Mac
They may sell lots of pro applications, but that doesn't equate caring about Mac users. And I don't even really care if they "care" about Mac users - I just want them to take pride in their product. That there is such a performance difference in Flash between Mac OSX and Windows should be extremely embarrassing for them. You can't tell me that if Adobe took this seriously that they couldn't go to Apple and that Apple wouldn't work with them. The fact is, Adobe isn't overly concerned with the Mac. They were content to coast. The whole 64 bit carbon thing should have been a non-issue. The writing was on the wall - if they were really serious about the Mac, they would have already been moving to Cocoa, instead of waiting until the absolute last minute when Apple basically forced their hand. Plenty of other developers made the leap to Cocoa without having to have Apple basically poke them in the butt with an electric cattle prod. Instead Adobe was plainly content and intent on "milking" the Mac. I think Apple saw this, along with all the hassle of propping up Carbon 64 and they said "enough - were killing it". It was the smart thing to do. It was the ballsy thing to do as to this day people are still painting Apple as the debil for it. Much like with Adobe and their half-a$$ed flash iOS app compiler, they only have themselves to blame - Apple was quite clear about the future of Mac OSX and the iOS - none of it was a secret. Snow Leopard wouldn't have happened if 64bit carbon was still lurching around like the zombie that won't die, and for all the jokes about "thousands of fart apps" what the heck do you think the ease of allowing "non-experts" to write thousands of poorly coded and un-optomized iOS apps would do for the iOS? I think Apple was exactly correct in their reasoning for blocking flash and Adobe's flash to app converter. Apple is about the user experience, and the user experience would have sucked with those tools.
If you want a platform with an uneven and inconsistent user experience, Android has your back! Knock yourself out. Have fun with unexplained battery drain, warm handsets, wildly variable battery life, uneven performance... Just remember the freedom to shoot yourself in the foot means you occasionally will.
I think Adobe got a double one-two punch from the iPhone that they didn't anticipate. First of all, they didn't expect Apple to literally take over the advanced mobile market overnight. And second they probably didn't expect the double digit growth in the Mac caused by first the iPod and now the iPhone "halo" effect.
They gambled they could milk the Mac and coast along on Windows. They gambled wrong. Oh well - man up and take care of business - but enough with the "life is so unfair". Please...