Apple hurting Adobe?
This is a discussion on Apple hurting Adobe? within the iPad General Discussions forums, part of the Apple iPad Discussions category; I think people don't quite understand... or don't care enough to understand. The code built in flash in CS5 that is put into the app ...
I think people don't quite understand... or don't care enough to understand. The code built in flash in CS5 that is put into the app store is NOT flash!!! They aren't disallowing flash code... they are disallowing objective-c code that just happened to originate in flash!
That would be like Microsoft not allowing people to install software on their Windows machines that were converted from Java to C# using the Java2C converter in Eclipse! Microsoft would never do that because A) it is completely harmless and B) there is absolutely no reason to! I get it... Apple wants to play the bully now and flex some muscle since they and Adobe can't seem to work out their problems. That's fine... they have that right. But people trying to justify it by saying it is to "protect" the iDevice system & stability have absolutely no idea what they are talking about and/or are confusing flash in the browser with app store apps that just happened to be coded in the flash tool BEFORE being converted to objective-c!
Last edited by brobar; 04-10-2010 at 01:14 AM.
04-10-2010 01:11 AM
Frankly speaking this is none belong to out business, who care in witch language is coded the appís you enjoy
Originally Posted by brobar
if tomolo Apple donít provide good devices, or useless appís all will turn to what that work
How many software company didnít convert their software in OSX ?? , now because iMobile become famous we listen complain from every corner
Apple decide what they want for THEIR PRODUCTS until they provide what we need Ö itís not more complicated than this Ö
if the developer are not satisfied nobody force them to code for iTunes they can go to see the competitor and propose them their knowledge
You hit the nail on the head... if the developers aren't happy with it they can/will look for another platform which is kinda sad. Don't get me wrong... I'm cheering for Apple here and want what is best for them (and the developers since I'm one myself). I just can't comprehend how Apple wins here though... there is so much possible revenue at stake here that Apple seems to be passing up for no perceivable reason. If there was a valid reason then I'd love to hear it but the only reason that carries any weight that people have thrown out there is Apple is only doing it "because they can" and if I were an Apple shareholder or on the board I wouldn't find that reason very justifiable when taking into consideration possible squandered opportunities at additional revenue.
Let's make sure that we make and keep the distinction between flash in the browser and app store apps that were converted from flash/action script to objective-c!
I understand completely the motive behind Apple not allowing flash in the browser. I get that from a monetary point of view as well as a battery life issue and a browser stability issue. But that isn't what I'm talking about. What I'm focusing on and questioning is what is Apple's motive and what do they GAIN by disallowing objective-c apps in the app store that were cross-compiled from flash? We all know that they CAN do it... but is there a reason for them to do it outside of "because they can"??? What do they gain from that? I've looked at it from every conceivable angle and I don't see a gain at all... only a loss!
Last edited by brobar; 04-10-2010 at 02:13 AM.
I understand you clearly, but i guess the shareholder know the real reason … Apple are like every company they want to make revenue and long term business
Originally Posted by brobar
Don’t you think if they can provide us the multi tasking early they will do ??
they took time because they want provide the best user experience possible
like the copy and paste, as Android didn’t have if i am not wrong ….
they have surely a reason, but they are not YET forced to disclose it
PS: i didn’t talk about you as developer , i talk about the one say he stop to develop for Apple
Please note this quote " The primary reason for the change, say sources familiar with Apple's plans, is to support sophisticated new multitasking APIs in iPhone 4.0. The system will now be evaluating apps as they run in order to implement smart multitasking. It can't do this if apps are running within a runtime or are cross compiled with a foreign [insert Adobe's software tool] structure that doesn't behave identically to a native C/C++/Obj-C app.
Originally Posted by brobar
"[The operating system] can't swap out resources, it can't pause some threads while allowing others to run, it can't selectively notify, etc. Apple needs full access to a properly-compiled app to do the pull off the tricks they are with this new OS,"...unquote.
That quote was from this link
AppleInsider | Apple's prohibition of Flash-built apps in iPhone 4.0 related to multitasking
Apple isn't out to screw Adobe, they just don't need the archaic crap that is interfering with moving mobile technology ahead.
Apple's unique approach to managed multitasking means two things. They are going to save that long life battery experience and everything should remain snappy for the user. Multitasking on Android and Win Mo becomes very sluggish when too many unregulated apps remain open each stealing the resources of the mobile CPU.
That is why an Android user must have access to a task manager to kill some of the unneeded tasks that are running in the background when Android becomes sluggish. Android never did not implement multitasking properly on a low power CPU. Here again is another area that Apple can patent to lock in their OS advances and permanently differentiate themselves from iPad wannabees.
Did you not notice the swipe Jobs made at task managers during the presentation?
Apple doesn't need developers on their side who can not grasp this. Let them work for someone else, they are unqualified to run with the big dog in mobile.
Last edited by 4phun; 04-10-2010 at 06:09 AM.
4phun .sir you have hit it on the head about the Adobe ..they do not want to go forward in the next step in the smart hand held device world of computering ..they can not figure that one out then they do not need to be in the market and need to go die off somewhere and be quiet about it..
it about the future and the future use of the small hand held computer system that are going to be comeing out in the next years by all the major players in the computer companys..
Apple has beaten them to the punch on this and soon as the whole figures this out Adobe will no longer have a chance for the companys are going to be dumping the adobe set up a more compact stream line O.S system to work in the future system..
H.P has done everything in it power to get the ipad and iphone shoot down with as many as they can bad reviews about the ipad ..
they are just -p---- off that apple has beaten them to the punch along with they are takeing the lion share of the market away form the cellphone companys with the apple iphone and now with the launch of the ipad ..every computer company out there is scambleing to get some form of a tablet out and onto the market to get a piece of the pie ..
So when can we expect HTML5 to go mainstream and fix this stupid dilema?
It's still being drafted and isn't even at the canidate stage. 2020 at best. Apple pushing it like this may help speed things up with more public preasure but there are still lots of things that need to be done. Has the h.264 VS. .Ogg codac fight been resolved?
I hand realized Apple was being very ***** about the new multi-tasking APIs. Why not just prevent non-open wrapper Apps from multi-tasking at all. Although I guess that would make users confused... perhaps mark them in GUI to indicate lack of Multi-tasking support so the user knows that it'll take all the resources and completly close when left.
Last edited by Dorje; 04-10-2010 at 09:44 AM.
Add 202 to my user number and call me an Airplane.
--iPad 2 64 GB Black WiFi "Dynabook 2011. With know-how and integrity"
How much you wanna bet someone will come up with a way to side load an app creating outside of the sdk into it to spoof creation.
Only allowing iPhone sdk for creation is a really stupid move on apples part. They basically just eliminated windows developers from the market. Not smart.
In a very complicated process that requires as much the art of divining as the skill of programming, Apple has learned some bitter lessons about telling too much, too soon. Other fields and manufacturers have learned the hard way about being too open with new products. For one thing, anything that is not tied down in patets, can be a source of lawsuites from many of the leeches.
Right or wrong, Apple has come to the conclusion that they must make a break from flash, and they are trying to keep from any way of having to deal with it because they think it will decrease customer experience. And the public does not understand the difference between flash and flash based. Apple is releasing the iPad now, but they are thinking about the iPad/iPhone of five years from now.