Linked by Thom Holwerda on Mon 21st Apr 2008 19:00 UTC, submitted by Adam S
Thread beginning with comment 310784
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.





Member since:
2007-02-05
"Look at all the trouble Adobe got themselves into by using Carbon."
Well, Carbon was never meant to replace the classic MacOS API's, it was just a quick way to get an old app to benefit from features on OSX and not have to run in classic mode.
It was IMO quite obvious that Carbon would eventually go away...
Adobe has only been "lazy"(not really lazy, but not willing to use resources on porting to Cocoa) and now they're seeing the consequenses.
This is a bit off topic: but a interesting side-effect of having to get Photoshop on a other API than Carbon might be that they now would choose a cross-plattform API such as QT, GTK or wxWidgets. If they do maybe the geeky dream of having Photoshop(or maybe even the whole Creative Suite!) on *nix will come true.
Probably not though. *Keeps on dreaming*
--------------------------------
Regarding that people should learn crossplattform I agree! I'm soon getting a Mac, and after being trapped in .NET I want to have something that's truly cross-plattoform, so I'm learning Python and wxPython.
On the other side there are some things, such as the drawer that (to my knowlegde, correct me if I'm wrong) can't get with crossplattform kits. (And other things mentioned in the article.)