putamare
RTFM
The GUI and CLI seem to be pretty natural divisions within OSX. I'm not implying the two will never get along, but each side is a little suspicious of the other. From what I've seen, the GUI crowd seems more opinion oriented (this browser is better than that one, spring loaded folders are/aren't needed, etc.), whereas the CLI bunch is more concerned with just getting it to work (I know this is an over-generalization, but the basic pattern holds true). Say some put-upon soul is trying to configure virtual servers on apache (yeah, I know there's a search button, but from my experience of reading these posts I think only about 10 of us know its there), and posts a simple call for help in the "Mac OS X System & Software" category. All too soon his post will be pushed to the bottom by the overanalizations of the latest .01 release of the beta browser de jour and could easily be missed by someone willing to give the poster a shove in the right direction (even if it is just to say that there is already a post in the "How-To" section). The fact that such an area wouldn't get as much traffic is exactly the point, a higher signal-to-noise ratio increases the chances of a relevant reply. I also think its a safe assumption that the concerns of someone working with perl, php, mysql, apache, etc., don't really mesh well with objective C & java programmers.
So, how about taking a cue from Apple? Split X discussions up into Interface, Developer, and Core OS (the displays and sound layer could probably easily fit in with the developer).
So, how about taking a cue from Apple? Split X discussions up into Interface, Developer, and Core OS (the displays and sound layer could probably easily fit in with the developer).