Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Any thoughts on Apple taking advantage of this and producing a Photoshop competitor? They have certainly pushed into the "pro app" category over the last few years and Photoshop is the one potential rival they have not dared to challenge.
 
Well that's crappy... If Apple isn't careful they could lose their fairly strong presence in the upper end of the graphic arts industry if a windows guy can mess around with massive photos 10 times faster than the mac guy.
Which is why we'll see Apple finally release the long awaited Cocoa Photoshop killer!!!! Adobe should have made the switch years ago, but they were lazy. Carbon was NEVER a long term solution,, but Adobe milked it for all it's worth. How many paid upgrades did they receive, yet they never REALLY re-wrote the code. Not to Cocoa anyway. I shed no tears for them.

With no reason to upgrade Photoshop for 3 years now, Apple has some time to build up a user base on a native, fast, clean new image editing app. Photoshop's days are numbered! (number CS4 and number CS5) Goodbye creaky old Carbon OS 9 code, hello APK (Apple Photoshop Killer)!!! Can't wait!!
 
Anybody who is ANYBODY in the Graphics field knows that a REAL designer/artist doesn't use a Windows version of Photoshop or Illustrator.

Companies that use PC's in their art departments are jokes. They like to use the "Cost & Support" excuse for not using the machines that were really meant to do these jobs. If you buy a cheap PC to run PS on, good luck getting it to do anything more than create a couple layers and some cloning.


ad populum, circumstantial ad hominem, generalizations, it's like a fallacy buffet!
 
If Adobe was too blind to see that Apple has been trying to kill Carbon for so long, then it's not apple's fault for coming out and saying Carbon64-bit was not going to be in Leopard. Adobe should have already been migrating towards Cocoa. It's called planning ahead. If you know there's going to be a transition, you start working on it as early as possible so when the day comes, you aren't caught with your pants down.

I don't know why they didn't start the Cocoa rewrite when they took it Universal.
 
Pft, bull.

The real reason, is because Adobe knows that when CS4 comes out, most Mac using PS fanboys (and those that need it for work) will want the (slightly) less buggy program so bad that they'll buy it, despite it not being 64bit. Then when CS5 comes out, well, same story. :D

I wouldn't be surprised if Windows users did it for the same reason XD
 
Many developers have been writing Cocoa apps for OS X, there's no excuse for Adobe to be lazy. This comes from the fact that Microsoft has done nothing to really change Windows so Adobe is used to writing the same code year after year. Microsoft gives them no reason for change so they treat Apple's customers the same way. Boo to Adobe.:(

To try and blame Microsoft in anyway for this is utterly preposterous. Treating your point as if it were even mildly feasible, how does introducing new technologies such as .Net and WPF warrant the claim that "Microsoft has done nothing to really change Windows"?
 
Pft, bull.

The real reason, is because Adobe knows that when CS4 comes out, most Mac using PS fanboys (and those that need it for work) will want the (slightly) less buggy program so bad that they'll buy it, despite it not being 64bit. Then when CS5 comes out, well, same story. :D
XD

Mac users will switch over to Apple's 64-bit Photoshop killer before buying upgrades to CS4 or CS5.
 
Adobe got lazy, plain and simple! Apple communicated MANY years ago that Carbon was transitional from Mac OS 9 to Mac OS X, and Adobe just dragged their feet on their Carbon -> Cocoa migration.

No more excuses, Adobe.
 
Well that's crappy... If Apple isn't careful they could lose their fairly strong presence in the upper end of the graphic arts industry if a windows guy can mess around with massive photos 10 times faster than the mac guy.

No, not really since most Graphics people are Mac people and we all know what happens when you drink the Apple Kool-Aid!

Also wouldn't a 64bit application require a 64bit OS and in the windows world that would be the 64 bit version of Vista. Not exactly a popular OS.
 
No, not really since most Graphics people are Mac people and we all know what happens when you drink the Apple Kool-Aid!

Also wouldn't a 64bit application require a 64bit OS and in the windows world that would be the 64 bit version of Vista. Not exactly a popular OS.

Or XP64. Or perhaps Windows Server?
 
Adobe got lazy, plain and simple! Apple communicated MANY years ago that Carbon was transitional from Mac OS 9 to Mac OS X, and Adobe just dragged their feet on their Carbon -> Cocoa migration.

No more excuses, Adobe.
Exactly! Apple wrote Carbon specifically for Adobe (MS and a few others) as a stop gap to help their transition. It was never meant to be permanent. Adobe got fat and lazy. Adobe invested nothing in Cocoa even though millions have been earned for upgrades over the years. I see the end of Adobe's reign of image editing on the horizon.
 
Mac users will switch over to Apple's 64-bit Photoshop killer before buying upgrades to CS4 or CS5.

Which doesn't exist. And seems unlikely any time soon.

If you REALLY think a new 64 bit app is on the horizon, can you explain why apple hasn't updated ANY of their pro apps to 64 bit yet? Not even Aperture, which is fairly new?

I bet we'll see it before the end of this year. Most likely it's already written. Just not released.

Give us a freaking break. What would ever give you that idea? There's no evidence from any reliable source that apple is even WORKING on a PS type app right now. "Already written". Idiotic.
:rolleyes:
 
As a CS3 customer, I really don't think a lot of people are going to be rushing to CS4. The main reason many of us moved from CS2 to CS3 was for the Universal version of the apps.

I've answered a half dozen surveys from Adobe about my upgrade plans and from what I've been able to gather, they really want to make upgrading to their new software an annual affair. However, in the real world, many of us are too busy to update our software like that, especially if they plan to make radical changes (ActionScript 2 to 3).

I honestly believe that the average CS3 user does not expect a suite upgrade (CS4) until sometime in late 2009.

However, we do expect bug fixes in free upgrades to CS3 until then.
 
Also wouldn't a 64bit application require a 64bit OS and in the windows world that would be the 64 bit version of Vista. Not exactly a popular OS.

Actually, there has been a 64 bit version of XP for a while. From what I've heard it's stable and there are a number of apps for it, certainly way more than the number of 64 bit apps for OSX (only about 2 or 3 major ones so far?).

Sadly, it looks like OSX has been lagging windows in terms of 64 bit apps, and with the cocoa/carbon fiasco it looks like OSX probably won't be catching up for a while.

Exactly! Apple wrote Carbon specifically for Adobe (MS and a few others) as a stop gap to help their transition. It was never meant to be permanent. Adobe got fat and lazy. Adobe invested nothing in Cocoa even though millions have been earned for upgrades over the years. I see the end of Adobe's reign of image editing on the horizon.

So since apple hasn't switched any of their pro apps over from the "stop gap" I guess Apple is just as fat and lazy? It's hard to take apple's carbon/cocoa recommendations seriously when they haven't yet followed them themselves.
 
Adobe have got their entire program written using Carbon where it's working perfectly well and then they found that they would have to rewrite a large part of it using Cocoa. Do you program? Do you know how long it would take to rewrite and debug over a million lines of code?

I do work as a software developer. a million lines is what I concider the border between large and "really big". It is where managers earn their pay. But I hope they don't have to re-write all of those one million lines. One would hope Adobe has a layer of abstraction of the Carbon API and that their core image processing cose is not hopelessly intermixed with calls to Apple's GUI library. If Adobe has this kind of horrable code then this is a great opertunity to toss it out. I would bet on them being smarter after all they already suport two platforms the move to cocca is like adding a third platform.
 
Wow people are talking out their asses about this.

First off, Leopard is the first real 64 bit OS Apple shipped, WinXP x64 and linux flavors have been out for quite some time. So there, there isnt some mythical apple head start on 64 bit, in fact they have lagged behind.

Second, off the top of my head i can think of at least 5 64bit apps that are more then just proof of concept, Houdini(which was just announced for the mac as a 64 bit app, maybe they will beat adobe), Maya, XSI, Lightwave, Max. two of the 5 apps listed there are also available for the Mac, not in 64 bit flavors. Both Autodesk(Alias) and Newtek, both said that when apple ships a 64 bit OS they will look in to shipping a 64 bit build of their applications.

Third, like mentioned before, converting from Carbon to Coca, must be a huge pain in the ass, which is obvious because Apple's apps aren't even Coca. And apples apps have been around for quite some time, and they would be best in the know of when there will be changes in the API.

Yes it does suck that it takes quite a long time for after effects to launch and it can be pokey at times, but have you used Motion? Such a slow app.

And for 64bits of coolness, unless you are working with GIANT data sets, you dont see that much speed boost. Going between Maya 2008 64 bit and the 32 bit one, unless i have very large scene files the render time isnt that big of a boost. I have a feeling it will be the same way with photoshop and after effects.
 
This is a poor excuse, especially when considering carbon actually took more code for conversion than does
Cocoa.

I agree. And as someone that uses CS3 daily, I can't see CS4 being as highly anticipated as CS3 was. Especially not Photoshop CS4. Photo editing isn't advancing at a rapid pace. I could understand Flash or Dreamweaver being updated but not Photoshop. At the high premium that Adobe software costs, I think its a little criminal for them to release a new version so soon. Luckily I don't have to pay for my software. But regardless, I think they should offer plug-in updates for new features for a few years before releasing totally new version. A little bit of loyalty to consumers that pay such a high price for their products would go a long way. Just imagine if M$ released service packs as a new OS. Or Apple releasing point (10.5.2 to 10.5.3) updates as a new OS. There would be endless threads complaining about this. Adobe is basically doing the same thing. And I didn't even rant about lack of 64-bit support. Shape up Adobe!
 
Straight from Adobe's John Knack

From MacWorld's forums:

http://www.macworld.com/article/132810/2008/04/photoshop64.html

Re: Photoshop CS4 to be 64-bit for Windows, but not Mac

leicaman wrote:
Understandable. But I hope Adobe doesn't wait until CS5 to release the 64 bit version for OSX if they finish it.

We'd like to provide more guidance about when we could ship a 64-bit-native version of Photoshop for OS X, but given the fact that no one has ever attempted a Carbon->Cocoa port of this size, we don't want to be irresponsible and provide specifics that we don't yet have. I mention in my blog post that we're targeting CS5, but it's simply too soon to make any hard and fast statements.

I can offer a little bit of history, though. When Apple moved from 68k processors to the PowerPC, Adobe offered a free update to PS 2.5. (Quark, as I recall, charged handsomely for the equivalent update.) Later, when the G5 came out, we offered a free update to Photoshop 7, even though CS1 was just six weeks off. (It would have been easy to say, "Well, to get that update, you have to buy the new version," but that's not how we wanted to roll.) Then when the PPC->Intel transition happened, the scope of the changes were too great to offer that kind of update, but I was able to persuade the company to do something it had never tried: releasing a public beta of Photoshop so that all current customers could get native performance six months earlier than would otherwise have been possible. It was quite a gamble, but it was the right thing to do.

I'm not saying that not being able to deliver a 64-bit-native CS4 for Mac isn't a drag; clearly it is, and if we had a way to change things, we would. All I can do is point to the Photoshop team's track record over the last ~15 years of Apple platform transitions. We'll keep working closely with Apple & thinking creatively about how best to deliver what Mac customers want.

Two other things, in case you don't want to wade through my whole blog post:

-- Let me reiterate that we respect Apple's decisions with regard to OS strategy. Just like the rest of us, they have finite resources and have to make tough calls. I don't want people to get the impression that Adobe is whining and pointing fingers. We're simply trying to give customers some insight into where things stand.

-- There are lots of ways to skin the performance cat, and 64-bit is just one among them. It isn't a magic bullet. I can't get into specifics now, but you'll see us doing more than ever to take advantage of Mac platform technology in CS4 and beyond.

Hope that helps,

J.
 
I have the cs3 master collection and have no plans to upgrade any more adobe software until it actually makes use of the ram and processors that my mac pro already has.
It will save me money and the cs3 aps are fine for me as they are now.
It will also be a real nice feeling to have my mac pro, which will probably be over 2 years old by then, suddenly get a huge boost in performance by having apps that can use lots of ram and processors.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.