• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Objective-C Question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Objective-C Question


  • Subject: Re: Objective-C Question
  • From: Jerry <email@hidden>
  • Date: Mon, 22 Sep 2003 21:39:35 -0700

I'm sorry, I have to chime in. I hope the mortally wounded horse will forgive me for one last thump.

The thing I love about Java is that it rigorously enforces standards. You are able to design an API and you can force your clients to manage all the things that can go wrong. You can rigorously defend your namespaces, and you can actively protect your code from being misused. As a Java programmer, the thing I like least about Objective-C is what a fast-and-loose language it is.

As an Objective-C programmer, what I like the most is what a flexible language it is. You can change inheritance relationships at runtime, for crying out loud. I can be incredibly productive in ObjC, but honestly I'm not sure how much of that is Cocoa, since that is the only framework I've used in ObjC. Let me tell you this, I like both Java and Objective-C, but I'll take Cocoa over Swing any time.

When I first knew I was a geek:
I was working on a project, using a Mac/Windows C++ framework. We got a new version of the environment and one of my coworkers had written macros to give us exceptions. When he explained what I cold do with them, I teared up. I love exceptions, probably a little more than is healthy. Sure, you can enumerate the different ways that things can go wrong, handle them differently, and pass them along if you can't fix it, but, at he risk of being repetitious, I love exceptions.

That said, Objective-C is a great, simple, flexible language. Working alone, ObjC is sweet. In a big bunch of folks, you have to be able to trust those around you to follow the rules. But if you can't trust them, why are you working with them? OK, you don't always have a choice. If you want your tool to enforce standards, Objective-C isn't for you.

Man, I love a language that doesn't get in my way. I love a language that lets me choose the right and wrong way to go about getting the job done. My design decisions are based on the right way to model the problem. Objective-C puts the decisions in my hands.

I do like exceptions, though.

Jerry
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: Objective-C Question (From: Steve Ehrenfried <email@hidden>)

  • Prev by Date: NotificationCenter, NSConnection, distributed notifications
  • Next by Date: IB problem with NSMatrix
  • Previous by thread: Re: Objective-C Question
  • Next by thread: Re: Objective-C Question
  • Index(es):
    • Date
    • Thread