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: Michael David Crawford <email@hidden>
- Date: Sat, 13 Jun 2015 17:14:37 -0700
I don't need either Swift nor Objective-C to code for OS X or iOS, I
need them to code for Cocoa or Cocoa Touch.
To code for OS X or iOS in C++ I can use ZooLib which I prefer quite a
lot to any other framework I've ever used.
Andy Green wrote in response to Apple's abandonment of Bedrock. If
Andy finds the rug pulled out from under as when Apple cancelled
64-bit Carbon he just writes a new low-level shim. I don't know but
expect ZooLib now talks directly to CoreGraphics, POSIX file I/O and
so on.
Ultimately the operating system is called by sending Mach messages to
it. There's really nothing that Cocoa or Cocoa touch can do that
ZooLib couldn't do better in ISO C++.
Michael David Crawford, Consulting Software Engineer
email@hidden
http://www.warplife.com/mdc/
Available for Software Development in the Portland, Oregon Metropolitan
Area.
On Sat, Jun 13, 2015 at 4:53 PM, Maxthon Chan <email@hidden> wrote:
> The language complexity issue of C++ is one of the main reason it put me off so much. And there is someone out there who posted a method of creating an iOS app with no Objective-C code at all but quite a lot of runtime abusing. The same method can be used on C++ but that requires some understanding how Objective-C code works under the hood.
>
>> On Jun 14, 2015, at 07:46, Graham Cox <email@hidden> wrote:
>>
>>
>>> On 13 Jun 2015, at 8:09 pm, Michael David Crawford <email@hidden> wrote:
>>>
>>> The problem I've got is that those who pay for iOS and OS X
>>> development have it in their heads that one must know either
>>> Objective-C or Swift.
>>
>>
>> You do need one of those to code for Apple devices, even if all your own code is in C++, because that’s what the frameworks use, and all the published APIs are expressed in. It’s a bit like the old days when you’d code in C or C++ but all the published APIs were in Pascal - you had to have an understanding of Pascal to follow the documentation at the very least, and to work with OS-defined data structures.
>>
>> For me, coming from 12 years of C++ to Objective-C in the early 2000s was a huge boost in productivity. A much simpler language can actually boost output because you spend less time trying to understand all the “features” you never actually need or use. YMMV.
>>
>> —Graham
>>
>>
>>
>> _______________________________________________
>>
>> 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
>
_______________________________________________
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
| References: | |
| | >Re: Language options: Objective-C, Swift, C or C++? (From: Roland King <email@hidden>) |
| | >Re: Language options: Objective-C, Swift, C or C++? (From: Quincey Morris <email@hidden>) |
| | >Re: Language options: Objective-C, Swift, C or C++? (From: Graham Cox <email@hidden>) |
| | >Re: Language options: Objective-C, Swift, C or C++? (From: Michael David Crawford <email@hidden>) |
| | >Re: Language options: Objective-C, Swift, C or C++? (From: Graham Cox <email@hidden>) |