Adobe and Apple, is it all over

[Scott Stevenson]

On Oct 9, 2006, at 4:35 AM, David Zhou wrote:

>> I'd take writing Photoshop from scratch in Cocoa over releasing 5  
>> major versions of Mac OS X in five years.
>
> My main concern here is that releasing a fully formed application  
> is very different from releasing APIs to developers.  It's just not  
> a very good comparison -- they are both time intensive, but in  
> different ways.

I'm not sure I follow? A Mac OS X update isn't just new API.


> Sure. But should Apple be the one to do it? You can argue that  
> Photoshop is already a best-of-breed application.

I disagree. Photoshop is not a shining example of a great Mac app.  
Adobe could make it a shining example if they wanted, but that would  
mean a change in thinking.


> Should all major apps for the platform be under Apple's wing? At  
> which point do you stop, and say enough, this one is for third  
> party software houses? More importantly, I'm not sure if I like the  
> current trend of thinking that for any sufficiently large  
> application, Apple should be the one to do it.

I don't care who makes it. If Adobe wants to make something I want to  
buy, more power to them.

I want an app designed for Mac OS X, or at least something that gives  
that impression. In my opinion, Photoshop does not.

I'm not willing to exempt Photoshop because it's been around for a  
while or because Apple already has several pro apps.


> I mean, eventually, it's entirely possible that the OS X platform  
> will end up having primarily first party applications with small,  
> focused, third party shareware.

Possible, but very extreme and very unlikely (not counting the  
distant future).

      - Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: /mailman/archive/macosx-talk/attachments/20061009/ddfc33d2/attachment.html