Here's an example: http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-i...
It's only a pain if you don't invest a week or so to master their use (which a knowledgable unix dev can also do in 1-2 days).
Installing "all databases and dependencies" on the Mac with Homebrew is not scalable, and it's not repeatable, and it's too kludgy. And when multiple versions of libs and such start to be needed, it wont even work.
(For small scale stuff, like some Wordpress development, it might be ok. But it would still be better to use a VM).
You won't deploy on a Mac in the end, but on some Linux box, so develop on a VM offering the same environment.
Note that I would still develop on a VM even if I was using Linux as a desktop -- you should not mix your desktop machine with your development environment.
Plus, many of the available database installs are much more fragile (and use older versions) on my Mac than they are on a VM.
The only time I see local development working particularly well is for front end development, where the part that matters is in the browser, not the server.
That would seriously restrict my ability to develop on the move or away from my desk.
Second, do you develop on the move unplugged for large stretches of time? Where is that place that doesn't have a plug?
I'm talking about host CPU
> Second, do you develop on the move unplugged for large stretches of time? Where is that place that doesn't have a plug?
Anywhere with sunshine and fresh air. We don't get many sunny days in the UK and I'm damned if I'm spending them indoors.