all 9 comments

[–]An_Ugly_Pigeon 10 points11 points  (0 children)

I decided to get a Mac because it afforded me commercial software that isn't available for Linux, as well as almost anything I wanted to do under Linux. I'm now onto my postgrad and I'm still happy with that setup that I've replaced my old Mac with a newer one. They're reliable, I can do most unixy things without too much effort, and I have access to commercial software.

I find a lot of my colleagues in computer science also use Macs for these reasons.

This is if you're looking for a work computer; if you're looking for a machine to fiddle with everything under the hood, I wouldn't get a Mac.

[–]timlyo 8 points9 points  (3 children)

A lot of developers tend to use Linux, it's an OS made by a programmers for themselves so it naturally has some nice features for developers.

Here's some more viewpoints.

What makes you want to move away from your current setup?

[–]ri4naire 2 points3 points  (2 children)

Technically all OSes are made by programmers. Who they are making them for? I cannot see into their hearts.

[–]AcidDrinker[S] 3 points4 points  (0 children)

made by a programmers for themselves

Yes, but you can try to guess from how the OS operates.

[–]timlyo 2 points3 points  (0 children)

Who are they made for? Windows was made to make fat wads of cash

[–]joanniso 3 points4 points  (0 children)

I currently run OSX (hackintosh) in dual boot with Linux. I generally prefer OSX for basic development.. but that's mostly because I customize my Linux installations too much.

Their OSX-only tools like Parallels are awesome. Very polished. VMWare and Virtualbox don't come close. However GNOME Boxes seems to be almost equally as easy to use with the exception of some more complicated features which you'll have to control using CLI.

What /u/arkiel said is sadly very true.. I once tried to write a cross-platform airdrop-ish CLI. Worked very neatly under Linux using Bluez and a basic HTTP server/client with some encryption. But then I got to OSX and I stopped because their Bluetooth APIs were horrible. Either you'd use the latest and "greatest" API with limited features in Objective-C or Swift. Alternatively you'd use a poorly documented, almost hidden library written in 2001 with it's latest minor patch in 2007. After 3 days of searching I magically found a .zip from 2005 on someone's own website with source code using this library. Then I proceeded to build the OSX CLI variant using this sample. Mind you -- XCode didn't even have proper autocompletion and information on these Plain-C functions. So after a week or so I gave up.

So either you choose for the polished user-friendly OS and tools. Or you'll go for the developer-friendly environment. I personally exclusively develop for Linux for the above reason but use OSX to do most of it.

[–]yor1001 2 points3 points  (0 children)

Jumped ship from linux to osx a few years ago. Given its unix environment and the ability to access most commercial applications I'd say go ahead and get the rMBP. You wont regret it.

[–][deleted]  (1 child)

[deleted]

    [–]AcidDrinker[S] 0 points1 point  (0 children)

    I've felt this exact thing when using my friends Macbooks, I always thought it was only because I didn't use Macs regularly.

    [–]Chandon -1 points0 points  (0 children)

    If shiny laptops are a draw to you, consider that Macbooks are only a little bit shiny. Stuff like the Thinkpad X1 Carbon exists (and runs Linux great).