I may have misinterpreted the WWDC ’14 announcement of Swift. Somehow I got the impression Swift was supposed to make Mac programming easier and more fun. What I found was that with Cocoa, it makes easy stuff harder without making the hard stuff the slightest bit easier. (In the case of string manipulation, it makes the easy stuff wayyyy harder.)
I am adopting Swift anyway because it cuts my number of source files in half. Having fewer places for bugs to crop up is more important to me than a language’s likeability. I believe I would be happier with an ObjC-3 that modernized the language a bit and did away with header files, but that’s not what we’re ever going to get—so Swift it is. -- Charles On Friday, June 12, 2015 at 20:51, Maxthon Chan wrote: > News outlets says that Objective-C is quickly falling out of people’s > attention and developers are turning away from it to Swift and C++. So what > language will you use to code various parts of your new project? Objective-C? > Swift 2? C++? Or the good old plain C? > > _______________________________________________ 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
