Originally Posted by hobbes-99
It's going too far for a U turn. I'd really hoped this would get sorted... As the spec of handsets gets better and better they're far more able to run flash easily
That's a worthless argument. Adobe has had almost 3 years to make Flash usable on mobile devices (more if you count pre-iPhone time). Why should Apple base their plans on Adobe's oft-delayed promises?
In addition, 'our software is slow, but hardware will catch up' has NEVER been a winning strategy. Software tends to bloat at a rate comparable to CPU improvements.
Originally Posted by GMHut
We get it, Jobs doesn't like Flash. Push Adobe to improve it. Push them to improve their design products. But for Pete's sake, I wish he'd stop poking them in the eye so publicly every chance he gets. All that will do is put their professional design customers in the middle of an unnecessary beef.
Adobe has had years and hasn't fixed Flash. Apple was happy to let it go at that, but have you seen all the Anti-Apple sentiment being drummed up and all the whining from Flash developers and Adobe? Does 'screw you, Apple' ring a bell?
Then look at these forums. Dozens of people who never posted to the forum before suddenly show up defending Adobe - even though most of them don't know anything about Macs or Mac OS X. Can you say 'Adobe shill'?
The noise was getting loud enough that Apple was right to defend itself by getting some facts on the table to try to counteract all the lies being spread. As just one simple example, how many times have you heard that Apple blocked Flash on the iPhone? Hundreds? Thousands? More? And, yet, there IS no version of Flash that is capable of running on the iPhone. NONE. And it's not just the iPhone - it's EVERY mobile device. There are no mobile devices that run full versions of Flash today - and even the beta only runs on the tiniest percentage of current phones. Yet Apple is being accused of blocking Flash. It was about time for Apple to set the record straight.
Originally Posted by backtomac
Apple doesn't need to tell developers how to write apps.
Apparently, they do. Some 'Developers' are apparently content to make crappy apps that don't work well. I believe I read that the largest reason for AppStore rejection was apps that just wouldn't run - something like 30% of rejections. Now, that's not all of them. There are some great developers - but they're already using Obj-C and don't have any complaints.
Apple's users expect a certain quality and want Apple to deliver it. If something works badly and their phone has a short battery life, Apple gets the blame - so Apple is entirely within its rights to set standards. You may not like the standards, but that's too bad. Go build your own mobile device. It's more important to Apple to keep CUSTOMERS happy than the small number of whiny developers who can't be bothered to learn any more than Flash scripting.
Originally Posted by SpotOn
The truth is Apple is going down a road of producing underpowered devices with less features with huge margins and is attempting to convert the entire web to fit their business model.
I wonder what planet you've been living on. When the iPhone 3GS came out, it was widely regarded as the fastest phone available. Some of the new Droid phones are starting to catch up, but side-by-side tests say that they're not ahead. And Apple has a new phone coming out in a month or so.
Less features is partially true, I guess. Apple focuses on the user experience. They made an iPad to be light, efficient and usable. If you think that a tablet is better with 4 USB ports, SD slot, CF slot, a few more memory card slots, VGA, DVI, parallel port, maybe a serial port, full blown desktop OS, and 3 pound battery, go ahead and buy one. That's not the objective for Apple. Apple is focused on providing the best user experience - and sometimes that does mean less features - so it's not a negative.
Originally Posted by mstone
PM me your username and login and I will play the game to test it. Otherwise link to an example that doesn't require payment to view. The demo is Flash with a lot of animations. Your first statement was that the page used NO animations, So does the game use animations or not?
You've already proven that you're a liar by claiming to have run the application when you didn't. Why should I give you my daughter's ID - so that she can find her entire platform erased?
You're making up lies again. I said that the page uses no animations - which is true. But the demo is quite different than testing it on the real thing. For example, my daughter's Webkinz world has 85 different animals and thousands of items in nearly 100 different rooms. Obviously, that's going to be a little different than running a demo. I guess the fact that you don't understand that means that you're incompetent - as well as a liar.
Regardless, it has now been established that you are a liar. You said that you ran the Webkinz game when all you did was run a game. Yet you used that silly 'test' to accuse me of lying because you only got 58% CPU usage (on a more powerful system than mine) when I got 120% running the full game. Sounds like you need to collect your check from Adobe and crawl back into your hole.
He's not just arrogant, he's dishonest and slimy. A company the size of Adobe should be embarrassed to have him making that kind of response.
Originally Posted by backtomac
I've no gripe with keeping Flash off the iPhone.
I simply contend that the new SDK agreement, limiting the way apps are developed, is wrong. Some tools which are used to develop good iPhone apps are excluded which may lead to some good apps being rejected.
I don't doubt that.
But it will keep a much larger number of crappy apps off the platform. If 99% of Flash apps are crap, I don't mind losing the 1 good app in order to keep the 99 lousy ones off the platform. Especially since the good app developer is free to write his app in code that will work even better than the Flash code. If he wants to make money off the app store, he will do that.
Originally Posted by jeffreytgilbert
you're buying into the lie that flash reduces battery life which it's proven not to.
OK, then maybe you can explain to me how Adobe managed to break the laws of physics.
When I run Safari and stay away from Flash sites or use clicktoflash, my computer never gets hot and CPU usage for Safari is 10-20% max. As soon as I go to a Flash site, the CPU usage shoots over 100% and the bottom of the computer gets very hot.
Now, if the computer is getting hot and the CPU is doing much more work, where is that coming from if not from the battery? I'm really interested in the mechanism they're using to create heat and power CPU cycles that doesn't use the battery.