Re: Crossposting in Omni and Apple mailing list (was: Re: Tooltips in NSTableView)
Re: Crossposting in Omni and Apple mailing list (was: Re: Tooltips in NSTableView)
- Subject: Re: Crossposting in Omni and Apple mailing list (was: Re: Tooltips in NSTableView)
- From: "David W. Halliday" <email@hidden>
- Date: Mon, 21 May 2001 08:12:02 -0500
- Organization: Latin AmeriCom, formerly Latino Online
Uli Zappe wrote:
>
Hi,
>
>
I'd strongly suggest that people do *not* crosspost in the Omni and
>
the Apple developer mailings lists (maybe apart from announcements
>
and such). Both, especially the Omni one, are high traffic lists
>
that are hard enough to deal with anyway, and crossposting
>
certainly doesn't help here.
>
>
If *all* people crossposted, having two lists would make no sense
>
at all.
>
>
If only *some* people crosspost, these people seem to feel their
>
questions are more important than those of others, not the best
>
attitude for a mailing list.
>
>
What do you think?
>
>
Bye
>
Uli
>
...
I think the problem is one of migration.
I think most of what goes on in the Omni list (besides stuff having to
do with the Omni frameworks) should be in the Apple Cocoa (and Carbon)
lists (especially when one considers the server problems they've been
having). The Omni MacOSX-Dev list (formerly Rhapsody... etc.) is more a
historic artifact of the fact that Apple, until now, had no appropriate
lists, so Omni filled the void.
A further reason I think the move should be made is the supposition
that Apple /may/ use subscribership/posting volume in the Cocoa vs. Carbon
lists as a gauge for which environment needs the greatest attention, and
which developers need to be catered to. After all, Apple is certainly not
going to be able to continue it's present parallel development of both
Cocoa and Carbon into the indefinite future---they are going to have to
either chose to drop one of them from continued development, or they are
going to have to base one on the other. How they choose will be, I would
expect, influenced by their perception of developer
acceptance/direction/whatever.
To the extent this is the case, we need to give Apple every reason to
believe that Cocoa is indeed important to the developer community, or it
may go the way of OpenDoc. (Even though I think that Cocoa is far more
important to Apple's long term competitiveness, I think they will have a
harder time seeing this if they don't see enough of the developer
community clamoring for it's continued development. They may consider
Carbon to be "good enough".)
Just my thoughts.
David email@hidden