Excuse me but this whole discussion is about Adobe not being able to port Flash to the iPhone/iPad.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Adobe to sue Apple now?
- Thread starter netnothing
- Start date
- Sort by reaction score
Excuse me but this whole discussion is about Adobe not being able to port Flash to the iPhone/iPad.
bingo. there was no prior contract to ever support Flash on the iphone OS or the convertor etc. So the only thing Adobe could try is anti-trust and monopoly abuse. But for that to work, the iphone would have to have a market strength to abuse and right now there's no smart phone with a major lead on the others. Even with the millions and millions of iphones out there, it's still only like 10% of the market, same as all other companies (give or take a percent)
I suspect that Adobe knows this and has no plans to do any such thing and this source is full of crap
You can't separate the two. Apple's apps only work on Apple's hardware since they don't license their OS.
Thanks for the random link?
Your opinion of whether Aperture surpasses Lightroom or not matters very little. I'm looking at the actual usage of both programs, in the real world, across a broad spectrum of photographers in multiple fields. Lightroom is king.
This is, of course, disregarding the fact that there's still a substantial percentage of photographers who use neither. It's still the Bridge/Photoshop world, with RAW editor/organizers serving no need at all.
I'll vouch for what this man said about Logic. Logic is my main DAW and I love that program but ProTools dominates the professional market. And Logic still has an amateur stigma associated with it - if you're a professional engineer telling pro musicians you record on Logic, you might as well say you record on FL Studio.
Actually...
It actually quite seems like it's the recent SDK blocking that prompted this increase in Adobe frustration. So, yes, this topic does revolve around the preventation of Flash-to-iPhone ports.
With Apple putting in the Opera web browser, the claim of "duplicated functionality" is now lost for that issue.
But I digress.
Adobe should rewrite Flash player to integrate with Objective-C. If Apple still has a fit and says "no", then there's a big lawsuit.
http://www.readwriteweb.com/archive...eat_flash_surprising_results_of_new_tests.php
Interesting article.
I'm siding with Adobe on this. With even Google siding with Flash, never mind how Flash is almost everywhere, I currently can think of anything that would go in Apple's favor.
That argument, especially as a means to sue, falls flat. No where in the SDK or in any replies has Adobe or Flash been called out specifically. In fact, Jobs has been very careful not to call out any companies by name. They are prohibiting all compliers that are just slapping a layer on top of another language, regardless of whether that language is Flash, Java, DOS or whatever.
i use them all everyday. well, i don't use FireWorks and i haven't tried Flash Catalyst yet, but the contents of the CS5 Web Premium package (FX(FB), FL, PS, AI, DW) are applications i rely on.
you know, except for the time when he publicly stated that Adobe is lazy and flash was a bad product.
There are three sides to every coin.
The right side.
The wrong side.
And your ( not you personally ) side.
While it's obvious that SJ hates Adobe and is being a major dick by banning middleware tools I have trouble finding anything illegal about that move. That being said I hope that the threat of litigation will make Apple reconsider their position.
Wrong. From the linked article (and all the others) that everyone is ignoring:
"But the final straw was when Apple changed its iPhone SDK (software development kit) license so that developers may not submit programs to Apple that use cross-platform compilers."
and this:
"Indeed, the net effect of Apple's licensing change, according to John Gruber of Daring Fireball, is to make it impossible to use cross-compilers, such as the Flash-to-iPhone compiler in Adobe's upcoming Flash Professional CS5 release."
*THAT* is what Adobe (and a lot of developers) are *really* pissed off about.
Well said. Though the older Macs did appeal to the publishing world than Mr & Mrs Gameplayeronaglorifiedcellphone.
But as a start-up developer, student, and full time employee, I want established standards and not to fiddle with a purported standard that's augmented by everybody else. (At least Sun stopped Microsoft from doing to Java what they did to other languages.)
I will continue to hope Apple buys Adobe.
I will continue to hope Apple updates the video card line for the Mac Pro.
I will continue to hope Adobe sells its offerings to Linux.
I will continue to hope the economy improves.
I will continue to hope I get a social life one day and not at the cost of acquiring a social disease.
Heck, I can hope Microsoft hires somebody competent and fixes the 20-page report of flaws I once compiled... (good luck to us all.)
If hope is all we've got, then I'm sure as well going to use it.
Totally different game. Microsoft abused Window's dominance as an OS to push an unrelated product on folks.
If Apple dropped all support for Windows users to use ipods, iphones etc in any shape or form forcing them to buy a Mac to have that stuff, then maybe you could say its the same.
Many of these things package a run time library into the distribution package, and Apple can detect these.
Oh I see, yeah that would be hard to miss lol, how much harder would it be to just write everything in Xcode though? Instead of cross compiling.
no. the apps that get generated are normal iphone apps. but they have some support libraries in there that are related to flash. apple are saying this is not okay.
i haven't used it, but a lot of people hate xcode for stuff like internationalization, among other things. also, objective C is a WEIRD, ancient language.
apple telling developers what toolkits they can use to develop apps in (while maintaining lockdown on the appstore, which is otherwise fine IMO) is a net LOSS for end-users.
It depends. I happen to think it's pretty easy to write a lot of stuff in xcode, but if I was doing a 3-D game or something I'd certainly want to start with middleware. Personally, anything that's done in Flash I think I can do better and almost as quickly in objective-C, but I may be deluding myself.
Well, Flash is almost everywhere - except ANY mobile devices. There are NO mobile devices that support a full version of Flash today. Even Flash 10.1 (which may or may not be out this summer) will only run on Android with Cortex A8 or higher - or a miniscule number of mobile devices.
Flash doesn't work on ANY mobile devices today, so what did Apple do wrong?
Except that it's not true. First, Apple NEVER allowed runtime layers or unapproved APIs. The 'change' in rules was simply a clarification of what everyone already knew. See the quote below. Second, there's no sign that Adobe has done anything to address the Flash deficiencies, so every indication is that it would be an inferior user experience.
If they were generating Objective C code, it would be acceptable. The problem is that that isn't what they're doing. They're effectively creating a runtime with private libraries - both of which are not allowed.
"The Packager is a tricky but fascinating way to get around Apples restrictions, said Tim Bajarin, an analyst with Creative Strategies."
Interesting that your article says that it's designed to try to get around Apple's restrictions. So apparently everyone DID know that Apple didn't allow this kind of thing and Adobe tried to do an end run.
So much for the "Apple changed all the rules without warning" nonsense.
Oh, and I notice that it also fails to say how well it works. Most reports are that it doesn't work all that well, anyway. Not surprising - Flash requires a much faster processor (Cortex A8) than the iPhone offers and no one expects that adding a runtime layer is going to make it any faster.
Maybe that's why Apple is doing this now, before they quadruple their market share, and then becomes the dominant player in what could possibly be considered a smartphone "market" according to anti-trust law.
How many years out would that be?
If Adobe waits until then (and is still in business), then they might be able to talk the government into a case against Apple.
Until then, while Apple is still a minority player, they can legally be as anti-competitive as they want to be to try and keep other companies from screwing up their platform's ecosystem.
Just like Joe's hot dog stand can refuse to sell flame-broiled burgers, even if he has the most popular food stand among several in the neighborhood.
Actually, I've read them all, and it's all just bunk. It's bullsh*t, and I'm tired of the Adobe astroturfers clogging up the internet (nice April 2010 account creation date).
Apple provides the tools and the API calls to make your apps work. Because Flash is rapidly losing relevance on the internet, Adobe scrambled to try to add some value to it by allowing you to make poorly running iPhone app exports from Flash. Great. The trouble is that Apple really and deeply believes in a certain customer experience and a slowly running battery hogging faked ui-elements app doesn't really fit into that vision. So, they blocked it. The trouble is that the seeds of this prohibition were always in the SDK agreement, and they only just with this most recent SDK change really clarified what they meant.
You see, the new multitasking ability in 4.0 allows the iPhone OS to do most of the heavy lifting and "deciding" how to control the CPU and memory usage of the apps as you switch around. If your apps aren't coded to use this properly, why would Apple want your apps on their platform?
Adobe has no leg to stand on with an internet claims of "apple blocked Flash on the iPhone" or "Apple abuses its monopoly". It's all crap. Apple isn't blocking Acrobat, it's not blocking Photoshop or any part of CS5. They didn't block Flash on OS X, and didn't block it on the iPhone OS either (there was no plugin that would run on a mobile phone).
So what you have is a bunch of Adobe fantrolls spewing filth on the internet and it's gotten old.
For a real developer, Objective C in xcode isn't a big deal. The real problem is people who are nothing more than script jockeys using Flash who consider themselves to be programmers. They're too lazy to learn Obj C, so they whine about how unfair the world is.