Objective-C, Ruby and Python for Cocoa

Re:Objective-C, Ruby and Python for Cocoa by protomyth on Sunday January 11, 2009 @01:00PM (#429343)

My biggest problem with Ruby for Cocoa work is that I enjoy the Smalltalk message passing syntax (keyword) more than the C++ syntax (object.name). The hacks to make it work right in Ruby do not look quite right.

Objective-C fills the place C++ or C# fill in the .NET platform world. It would be interesting to see a language built for Cocoa that fills the VB role.

[ Parent | on HN ]

Re:Objective-C, Ruby and Python for Cocoa by tptacek on Sunday January 11, 2009 @02:34PM (#429441)

I had the same reaction, but ObjC's method names are so bad that I just wound up writing my own Ruby wrappers anyhow, so most of my code is written in Ruby idiom.

ObjC does not fill the role C# fills in .NET. ObjC is still C code. C# doesn't have pointers. It doesn't segfault. Every object has reflection. There aren't aliasing problems. ObjC fills the place C++ fills in Win32; we still need a C# replacement.

[ Parent | on HN ]

Re:Objective-C, Ruby and Python for Cocoa by protomyth on Monday January 12, 2009 @05:06PM (#431233)

Well, I was going with the C++/C# is the "do more" option and VB is quicker / easier.

Just a note: ObjC has reflection.

[ Parent | on HN ]

Re:Objective-C, Ruby and Python for Cocoa by tptacek on Tuesday January 13, 2009 @11:09AM (#432168)

For ObjC objects.

[ Parent | on HN ]