The question in question is Extracting latency value from output of ping.
Should questions like this be considered off-topic? Aren't there other SE sites dedicated to these types of questions?
We do encourage AppleScript, Automator, and UNIX shell scripting questions as well as how to use tools like Xcode for non-language specific tasks
So yes these kind of questions are absolutely on topic here.
Now, if the question is: Should we allow them in the future? Opinions may differ, but from my point of view it's often rather difficult to differentiate between scripting questions around specific OS X features (e.g. how can I list all connected USB devices) and questions which are generic enough to belong to another site (most probably Unix & Linux). Also, if the question does require a very detailed Unix knowhow not available on AD, we still can migrate it over if it doesn't get answered in due time. In other words: I don't see a pressing need to change the policy here.
Just because command line tools such as these are also used in other OS, often for much longer than they have been in OS X, doesn't mean they are not a part of OS X, provided, supported, licensed and documented from Apple directly.
A lot of the time where this sort of thing could be applicable to many SE sites, it comes down to where the OP feels most comfortable asking. If someone has a question on
ping or similar, but they happen to be using a Mac, then I'd feel bad pointing them at SuperUser where they might get savaged (for want of X better phrase)
As a Mac user who mostly "lives" on Unix & Linux stackexchange, I thought I'd provide my viewpoint on this.
Questions about command line tools (that aren't Apple-specific) are perfectly on-topic both here and on Unix & Linux. Most such questions are also on-topic for superuser.com. The main difference is the type of answers you're likely to receive.
Realize that a huge percentage of Unix & Linux questions relate to the command line, and frequently active users include many professional sysadmins, not to mention several people who actually write shells. This means that a well-written question about a command line tool may get a much more in-depth answer than you're likely to find on any other site.
Now, some people (most computer users, actually) aren't interested in really learning the command line; they primarily use a GUI and if they ask a question about the command line at all, what they would actually prefer is a simple command that they can paste into their terminal, which will do what they want, and let them get back to using the GUI. (This is fine, of course; not everyone needs to learn the command line. We have those people at Unix & Linux also.) This isn't the sort of answer that's considered "good" on U&L. It's probably not considered "good" here, either! But in-depth answers about the command line are really the norm on U&L. So if you have a tricky, highly technical command line question, U&L is (in my opinion) the best place possible to ask.
However what goes along with this is possibly less lenience for newbie questions. It's really hard to describe this, though, because no one is rude about it...I've rewritten this paragraph five times and I still can't quite nail it.
I suppose the closest I could come is to say: imagine the response of a bunch of (polite) doctors who were sitting and chatting if you came in and asked, "I forget, is it the ears or the eyes that are the 'sight' organs?" They'd answer you, of course, but they would undoubtedly be amused and might even chuckle at your naiveté. :)
So really, ask where you feel comfortable asking, and where you think you will get the best answer. Either way it's on topic.
My two cents on this, since Mac OS/X is based on BSD there is enough subtle difference between how commands work in a OS/X Terminal vs. a Linux-derived terminal. Because of this I would recommend allowing general purpose OS/X Terminal command questions here.
Having said that, when I worked for Applecare, first-tier support advisors are NOT allowed to freelance on the command-line, they are only allowed to use terminal commands if they come from an official Apple support doc, and that's rare!
Once I graduated to tier 2 ("Senior Advisor") I thought, woohoo I can solve problems a lot faster! Well there was more freedom (and depends on your manager) but there was still a strong emphasis on solutions the customers could understand that used GUI tools. True, customers get ahead of support agents and can do some damage when they "know enough to be dangerous," so keeping them away from the command line was generally the right thing to do ... until I talked to a customer who I knew was smarter than me :)
Well I only rehash that (no longer work there) to point out that Apple culture is, as noted in other answers, generally to stay away from the command line.
But having said all that my original point stands, and there is enough difference between BSD and Linux that the content can be reasonably dissimilar. I come from SunOS and still type ps -auxww, thankfully in Linux that still works. There are whole articles written about the differences in how ping works ... on other SE sites :)