Hi Jens, > On 3 Oct 2019, at 20:04, Jens Alfke via Cocoa-dev <cocoa-dev@lists.apple.com> > wrote: > > The people I hear complaining about this are those who, like you, didn't move > to Cocoa. Carbon was a _temporary_ transition API*.
It wasn’t clear to us (outside Apple) that Carbon was a temporary API until 2007, when Apple suddenly abandoned 64-bit Carbon. That might have been a good decision from Apple’s perspective, but we found it was extremely difficult to convert a large Carbon (C++) program into a Cocoa (C++ / ObjC) program. We attempted to do this (starting in 2007) and we failed. There were various reasons for this failure - but in the end (starting in 2017) we decided to do a complete rewrite using Cocoa and Swift. I know there are large companies that successfully moved from Carbon to Cocoa, including Apple itself. iTunes and the Finder became Cocoa programs at some point. But I don’t think it was easy for small companies with large/complex programs. Personally, I think that Cocoa is a much better framework than Carbon ever was. But I wish that Apple had made it easier to transition from Carbon to Cocoa. Jeremy _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
