• 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: PICT control problems [SOLVED]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PICT control problems [SOLVED]


  • Subject: Re: PICT control problems [SOLVED]
  • From: John Lunt <email@hidden>
  • Date: Sat, 24 Jun 2006 20:07:57 +0100

Whoa! Didn't want to start a Cocoa/Carbon argument, which is why I stressed that my reasons were personal. I think its great that there are lots of third party apps written in Cocoa for the Mac, its just I'm not sure yet that its the right way for me to go.

On 24 Jun 2006, at 16:28, Bill Bumgarner wrote:

This is starting to go afield of Xcode-users on-topic....

On Jun 24, 2006, at 9:45 AM, John Lunt wrote:
1. Cocoa is a bit of a niche - which is fine if you are doing it full-time but this is my hobby, so I (personally) don't want to learn something of limited applicability elsewhere.

I'm not sure I understand the reasoning here. Any system that can run a Carbon app will also be able to run a Cocoa app, save for the last remaining handful of people still running Mac OS 9. As such, Cocoa is no more of a niche than Carbon.


For new development on Mac OS X, you should generally use Cocoa. Carbon isn't going away any time soon, but it also isn't the target for new technologies and frameworks, either.

As well, you generally have to write a lot less code to get the same basic stuff done in Cocoa vs. Carbon.

I can accept this if you think you are always going to develop for the Mac, but C/C++ has served me well on Solaris, Windows, and OS X over the years. The fact that all the computers in my house at present are Macs is down to Apple having hit a sweet spot with good engineering and software that is pleasant to use. I've no idea what I'll be using in another 5 years, but I'll bet money you can program it in C. Similarly I think time spent on GCC/GDB is not wasted, as I'm betting that they will be available to me going forward.


The thing that really appeals to me about Cocoa is being able to extend the Apple software without starting again from scratch (i.e. PithHelmet or 'Letterbox' for Mail). The thing that puts me off is not learning the syntax (which look OK), but not knowing the subtleties (like the exception handling sub-thread that has kicked off here). I'll probably lurk in Cocoa-dev for a while, and as I said in another reply, I'll review in 6 months time.

I'm going to stop now, as I think I've got too far off topic.

Best wishes,

John.

_______________________________________________
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


  • Follow-Ups:
    • Re: PICT control problems [SOLVED]
      • From: Steven Fisher <email@hidden>
References: 
 >PICT control problems (From: John Lunt <email@hidden>)
 >Re: PICT control problems [SOLVED] (From: John Lunt <email@hidden>)
 >Re: PICT control problems [SOLVED] (From: Scott Thompson <email@hidden>)
 >Re: PICT control problems [SOLVED] (From: John Lunt <email@hidden>)
 >Re: PICT control problems [SOLVED] (From: Markus Hitter <email@hidden>)
 >Re: PICT control problems [SOLVED] (From: John Lunt <email@hidden>)
 >Re: PICT control problems [SOLVED] (From: Bill Bumgarner <email@hidden>)

  • Prev by Date: Re: Scripts Menu ReplaceAllText Causes Editor to Break?
  • Next by Date: java
  • Previous by thread: Re: Objective-C++ Exceptions (was: PICT control problems)
  • Next by thread: Re: PICT control problems [SOLVED]
  • Index(es):
    • Date
    • Thread