Ask HN: is devving on OSX legit *nix experience?

I developed on Linux for 5-6 years before switching over to OS X on my main machine.<p>Installing xcode (3 is free, 4 costs a small fee) gives you GCC4 on the command line, plus some other tools/libs. Note: I've never actually used the xcode IDE, I use Emacs.<p>You can also install a rootless X11 server and run X applications in it. Wine on mac actually uses this, and I've been using it to play Homeworld 2.<p>Most of the cross-platforms IDEs that you would probably be using (if you're that kind of guy) in Linux are available on mac. Take a look at QtCreator, Eclipse, Netbeans.<p>Mac comes with Java and Python installed. If you do C/C++ development the only real differences are that some libraries are installed as "frameworks" instead of in the usual /usr/lib (eg. you link with -framework OpenGL). Also the dynamic libraries are dylib's instead of so's (and consequently, DYLD_LIBRARY_PATH).<p>Mac calls multiple desktops "spaces", and they work pretty much the same as in Linux/Gnome.<p>Grep/awk/sed/etc all work pretty much the same as in Linux, although I think they are the BSD versions instead (whatever the reason, they are a little bit more picky about command line options).<p>Mac's Terminal.app compares favorably with Gnome's terminal (including tabs, transparency) and has some nice looking built-in themes.<p>Anything else, just ask. :) If you've used Ubuntu recently, switching to Mac may give you deja-vu.

I have a couple of friends who switched to the Mac to get away from WindBlows and Cygwin when developing, while retaining a good every-day platform with cool commercial software available. They have never looked back to WindBlows, or felt like they should be using Linux.<p>I tried to dump Windows by moving to Linux for my every day OS, but found doing some simple non-dev stuff (synching my PDA properly) too painful.Windows was bad enough that I took the leap and bought a Mac, and have loved it for development as well. I have done mostly command line dev, and IDE-oriented dev, and both are great on the Mac. The advantage over Linux is not cost, of course, but the everyday "It just works" experience and the availability of commercial software like Photoshop. And it is plenty Unixy, if you don't mind the fact that things like user accounts aren't managed just like Linux or base BSD.<p>I think it is the best of both worlds and would highly recommend it.<p>Brian

If you want the unix experience, stay in the shell. Use vim or emacs and become a passionate follower of either of those religions (but not both; nobody likes a cleverdick).<p>Actually, it's hard to do powerful things in OSX without using shell commands, just like it's hard to do in any graphical environment. But once you drop to shell, it's all unix.<p>That being said, use the right tool for the job. If you're writing mac or iOS software, use Xcode.

It's nix plus a bit more. I'm not aware of anything the GUI does in Linux that it doesn't do in Mac. Some workflows will be different, such as xcodebuild, but everything else like svn, git, cp, mv, make, sudo, nano etc is the same. You can do without Xcode, cdto and a Cocoa-only text editor, but don't put yourself through it.

If you use the command line tools like make, gcc, scripts, autoconf, etc., then it's almost exactly like developing on Linux/Unix.<p>If you use Xcode, then not so much... though it's still more like Linux/Unix than Windows.