3 ms·
I had tons of issues trying to get Postgres to work on my Mac. Lots of other conflicts, too. I think the Mountain Lion OS upgrade fried my host dev environment
by taude 13y ago
I had tons of issues trying to get Postgres to work on my Mac. Lots of other conflicts, too. I think the Mountain Lion OS upgrade fried my host dev environment, too. Eventually, I went the VM route....afterall, you're going to eventually deploy to a Linux box anyway, and there's enough differences that you'll feel the pain when you go to deploy.
And now, I don't have a polluted host OS with tons of versions of software. I can easily try out new technologies, kill the VM, and start over.
Keeping VMs for different projects in their on silo'd around is really convenient.
Switching OSes or upgrading, rebuilding a computer, etc. I don't loose these configurations.
The list goes on and one.
RAM is cheap. I think I paid $100 to upgrade my Mac Book Pro to 16 GB.
I can also switch back to a host Windows machine and take my VMs with me (should the need arise)
- workhere-io 13y agoI had tons of issues trying to get Postgres to work on my Mac Did you try http://postgresapp.com http://postgresapp.com ?
- taude 13y agoYes, I actually have that installed. Back when I was originally trying to get it to work, that wasn't available.
- bluedino 13y ago>> RAM is cheap. I think I paid $100 to upgrade my Mac Book Pro to 16 GB. RAM was cheap. Prices have went up a lot. Most DDR3 prices have almost doubled since this past spring/winter. 16GB laptop kits are ~ $140 when they were $75 a few months back. Still relatively cheap, though. Not to mention Apple only makes 1 laptop that you can add your own RAM to nowadays (13" MBP). It's $200 to go up to 16GB on a Retina.