What if death comes before victory?Go Steve! Fight to the death!
What if death comes before victory?Go Steve! Fight to the death!
Other than for Job's petty vendetta what possible reason could there be for this?
I'm so sick of Adobe and making bloatware and crap. I have no Adobe products on my system, and only Silverlight (Netflix) from Microsoft. I find that my computing time is better spent without software from those two companies.
Indeed. My cousin has spent several months developing a game with Unity, only for Apple to turn around and do this. He doesn't know yet, but is unlikely to be very happy.
Good. Apple putting the deed into their creed.
This HTML5 stuff is real, folks.
Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).
Adobe not supporting OSX wouldn't be helpful to Adobes clients either.![]()
As always Gruber is on point and insightful:
Why Apple Changed Section 3.3.1
The people that think it has anything to do with ads are missing the point, Apple will be the middle man in iAd so why would they care if the ads are delivered in HTML5 or Flash. Same with native applications, considering those factors I think John's line of thought on this is pretty accurate.
For all the people saying, "Die Flash, Die Flash" - have you ever stopped to ponder the fact that you would not have to download any of these flash apps?
[Didnt think so]
Therefore iphone will be snappy and if it isnt, you wont have flash to blame.
Those that would then say, "Its Apples product and they can do what they wish" - well, not true... its a public company so they need to be mindful of what the public want and offer a choice. [you dont want it, fine you dont have to download it, just like you dont have to download flashplayer on your mac... but if you do, its there for you]
Its called choice.
Peace
dAlen
I wonder how long until Apple refuse Opera Mobile.
I honestly have no clue what would I do if I was in their place - what Steve did yesterday was very close to check-mate move unless, of course, Adobe comes back with something equally offensive but I really can't see them doing that...
Here's what I would do I was Adobe: I'd officially drop the support for Mac OS X and offer all current Adobe customers that use Mac OS X free Adobe CS crossgrades to Windows.
That move would effectively destroy Apple's last position in the pro market. With Adobe CS gone, Apple would become a pure consumer company.
But this latest stupid Apple move is not only targeted at Adobe, it's also targeted at Unity and MonoTouch. These products are successful because you can use mainstream languages to program your iToy apps, and you do not have to use that ugly, 1980s Objective-C language that nobody else on the planet except for Apple uses.
In Unity and MonoTouch, you can use C# - and that was designed by Microsoft, which is company that actually understands what developers want. But of course Apple cannot accept that Microsoft controls a language that can be used to write software for their iToys. Especially not if that language and the development tools available for it are so much better than the outdated stuff that Apple offers.
This new restriction is a demonstration of fear, and it will cost Apple a lot of developers.
Here's what I would do I was Adobe: I'd officially drop the support for Mac OS X and offer all current Adobe customers that use Mac OS X free Adobe CS crossgrades to Windows.
That move would effectively destroy Apple's last position in the pro market. With Adobe CS gone, Apple would become a pure consumer company.
But this latest stupid Apple move is not only targeted at Adobe, it's also targeted at Unity and MonoTouch. These products are successful because you can use mainstream languages to program your iToy apps, and you do not have to use that ugly, 1980s Objective-C language that nobody else on the planet except for Apple uses.
In Unity and MonoTouch, you can use C# - and that was designed by Microsoft, which is company that actually understands what developers want. But of course Apple cannot accept that Microsoft controls a language that can be used to write software for their iToys. Especially not if that language and the development tools available for it are so much better than the outdated stuff that Apple offers.
This new restriction is a demonstration of fear, and it will cost Apple a lot of developers.