Every question posted on this list has the potential for an answer
using Cocoa.
"It's easier than you think." is precisely the kind of opinion best
kept off this list. You don't know anything about me.
I don't think you're being fair. The reply was completely appropriate
in terms of the OP's original question. The OP asked if it was
possible to port his existing Carbon-based Mac application over, and
the unsurprising answer was that it's not. Given the differences in
the UI, you'd have to make changes anyway, so volunteering that
writing your UI in Cocoa isn't impossibly difficult isn't saying that
"Cocoa's the best thing since sliced bread and you're stupid to be
using anything else."
I sit down everyday and have many years of meaningful Carbon
development work ahead of me, regardless of what future steps Apple
takes, or any arguments people may make, or what names some want to
call me. This list is about the only place we can discuss it and
even here we are bombarded constantly by the NSIrresistibleCharms
of Cocoa. I don't know how it works on other lists, but I don't
want to end every thread with a discussion on the magnificence of
Cocoa.
This isn't really relevant to this thread; it just sounds like you're
saying, "oh, pitiful me." And you're hardly bombarded by discussions
of the "magnificence of Cocoa;" typically the only time it comes up
in this list is when someone runs into something they can't do in
Carbon, just like...
I have often felt that the very existence of an alternative was
offensive to some Cocoa people, and it turns out my fears were
perfectly justified. Nobody would ever dare make a post in Cocoa-
Dev and say "Consider using Carbon." because it would be
harpooned. Nobody subscribed to this mailing list to learn about
Cocoa.
...there are certainly a number of Cocoa/Obj-C purists on cocoa-dev
who say "ewww" when you suggest using one of the Carbon [Core] API
routines to perform a task that can't be done in Cocoa. Most people
just take the information and use it to get their code working...
after first wrapping the unclean bits in a nice class category
wrapper. :)
Look, the only sure thing you know is that Apple has made the
decision that Cocoa is the preferred development framework, at least
for UI stuff, but that was news in 2007. Attacking someone for using
the C-word here doesn't change the realities, and doing so isn't even
attacking the messenger let alone the decision makers, just someone
who's trying to be helpful. And who might be inclined to be less so
in the future for fear of having his head bitten off were he to say a
politically incorrect thing.
That doesn't do anything to foster the cooperative environment that
you need here to get information moved around. Plus it makes you look
like a Carbon purist.
Finally, lest you categorize me as yet another Cocoa apologist for
defending one of "them," let me set you straight. I've been doing Mac
programming since the days when you needed a Lisa/MacXL to compile
your Pascal program and then copy it over to a Mac 128K on a floppy
disk because there weren't any native Mac compilers yet, then through
Carbon and support for OS X. If you've used a Mac for long, you've
used my software.
I was upset like everyone else after last year's announcement of no
64-bit support for Carbon UI, but after wading through a couple of
months of rants here, it was really clear that the decision would
stand. So my existing software is remaining Carbon, and any new
development is using Cocoa for the UI and a lot of nice Carbon Core
features (FSRefs and nifty stuff like that) underneath; seems like a
reasonable balance. I'm not great at Cocoa just yet, but getting
there. I haven't had a slap-my-forehead epiphany about Cocoa.
Ultimately they're all just tools to get a job done. You work with
the available tools or you go play in somebody else's sandbox.
My two cents...
steve
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
