| From everything I can see the underlaying object model of the OS hasn’t changed. If you want to continue using objective-C then it looks like you just keep using objective-C.
Objective-C is hardly the world’s most beautiful language. It slaps all of the baggage from C on top of a cool smalltalk-like object model and runtime. You could summarize it as smalltalk with buffer overflows and memory management issues.
I for one am looking forward to a supported application language for OSX that has generics, bounds checking, and memory management while interfacing easily with the Objective-C object model/runtime. It seems like a good alternative to slapping more-and-more features onto Objective-C. It’s already become which already seems to have become something of a wart-covered peccary with dental issues.
-jeff
On Jun 3, 2014, at 17:14, Gordon Apple < email@hidden> wrote:
My response was “Oh, no! 567 pages (iPad Retina portrait mode) of more s*** I have to learn.” One of the main advantages of Objective-C was that it was loosely typed. Now, it looks like we’re going back to a strongly typed language, nested functions (a la Pascal), everything is (or at least acts like) an object, etc. I’m not at the conference, so I’m hoping the vids will expound on the rational for this highly disruptive change and show where it really buys us an advantage.
On 6/3/14 9:18 AM, "email@hidden" <email@hidden> wrote:
I can't comment yet, I just haven't read far enough and tried it out to see if it replaces enough of ObjC for it to be a replacement. You still need C down there somewhere at the least. I need to find the Swift-interface-C chapter.
And if it does, I *still* don't know why. ObjC is an ok language, it does what it does, you learn it, you use it.
On 3 Jun, 2014, at 10:08 pm, Akis Kesoglou <email@hidden> wrote:
> On 3 Ιουν 2014, at 17:03, Roland King <email@hidden> wrote:
>
>> ... With some ObjC thrown in there too with the named/typed parameters. ...
>
> And that's exactly the reason I see ObjC being deprecated. From what I've read, Swift *feels* a lot like ObjC -- init/dealloc, designated initialisers, named function arguments, ARC, verbosity, etc.
>
> Akis
>
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|