Re: Language options: Objective-C, Swift, C or C++?
Re: Language options: Objective-C, Swift, C or C++?
- Subject: Re: Language options: Objective-C, Swift, C or C++?
- From: Britt Durbrow <email@hidden>
- Date: Fri, 12 Jun 2015 23:51:42 -0700
My $0.02:
Swift is too immature to warrant doing anything serious with it yet… it just hasn’t been around long enough to be exercised the way that Objective-C has. This will, however, change with time. And yes, there is something of a chicken-and-egg problem there: if nobody does anything serious with it, it’ll never achieve the level of maturity to warrant doing serious projects in it. I believe however that given time, enough people will pick it up and bang on it to overcome this issue.
Personally, if I had the time to dedicate to it, I’d come up with some non-critical project (i.e, something not “serious”, but big enough to qualify as “non-trivial") to do in Swift for the purpose of developing that skill set. (Perhaps when I get done with this project that I’m up to my eyeballs in right now… <sigh>).
I don’t see Objective-C going away anytime soon; just as I don’t see C going away anytime soon; or for that matter, C++ or Assembler. They all have their place, and there is a *massive* body of existing code written in those languages (admittedly, Assembler accounts for a tiny fraction of the codebase, but it is an absolutely essential fraction: the machine wouldn’t even boot without it; objc_msgSend is in it, etc).
And I trust the media approximately as far as I can throw them (seriously… have you *seen* what passes for reporting these days?!?!?).
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden