I joined this list looking for the latest info on issues (bugs) that
other OS X developers were finding so I could work more efficently. It
costs me about the same effort to write 1 line of code, or write 10
lines of prose, or read 100 lines. I've spent way too much of my
limited time scanning all this launchd debate and emptying my email
inbox. At this rate, reading all this dogma and reminiscent dialog
about how things should be is less effective than blindly coding around
any OS related problems I encounter.
Am I on the wrong list?
Where do the real programmers (with tight schedules like mine) exchange
useful info?
Here. It's just that Darwin has no bugs, so we had nothing else to talk about.
;-)
Seriously, if you want to read about a variety of Mac OS X (not just
Darwin) programming issues, join the OmniGroup macosx-dev list.
-pmb
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
