Somewhat tangentially related, a Sass I worked at, most devs preferred MacBooks for their dev boxes (ruby on rails + Java). At the time, Windows 8.1 was out. Ou

Somewhat tangentially related, a Sass I worked at, most devs preferred MacBooks for their dev boxes (ruby on rails + Java). At the time, Windows 8.1 was out. Our target runtime env was Ubuntu. I preferred to do all my development in a linux VM. I was constantly finding bugs that were checked in because they assumed the other devs assumed that their Macs mirrors the deployment environment. Except, it didn't Most common culprit was case sensitivity issues. APFS, by default, like NTFS, is case insensitive, unlike most common Linux filesystems. APFS can be made to be case sensitive, but it turns out, breaks a non insignificant number of Mac targetted apps. Of course, this breaks when you have a case difference when deploying to Linux. E.g. cannot import a ruby module because of a case difference in a filename. In my experience, the belief they were running on a *nix meant my fellow devs thought they were immune to fuckups they associated with Windows, but they were wrong and abstinent/arrogant about issues when confronted about it, by me, because I was running Windows (although running our code in a linux VM). I hope thats not everyones experience, but that was my one experience with Mac users targeting Linux for deployment. Seriously had a hard time convincing them there were problems because "it works on my machine," to which of course I responded "deploy it and run the tests again." To;Dr; MacBook != Linix laptop. Gets you maybe 95% of the way there. Still better off using a linux VM than relying upon same behavior between OS X and Linux. Besides, OS X is not even linux based. It's originally based on Net BSD (I have no idea how far the kernel, etc have deviated since).