3 ms·
I've had the opposite experience, typically. At an old job, I was trying to use a Windows 7 workstation for the same tasks as I'd use my GNU/Linux-based home w
by yellowapple 12y ago
I've had the opposite experience, typically. At an old job, I was trying to use a Windows 7 workstation for the same tasks as I'd use my GNU/Linux-based home workstations (and the Macbook I'm using at my current job): running VMs with VirtualBox, running local installations of PostgreSQL, etc. Windows was the more painful one, for me at least.
Granted, I'm not a fan of OS X by any means; far from it. However, the one redeeming quality is the fact that it's Unix underneath all the buggy Aqua and Finder and Cocoa and such, so at least I'm able to set it up with MacPorts (and/or Homebrew) and get some proper work done with it just like I would on any other Unix-like OS. You can't do that with Windows, at least not easily (and certainly not as painlessly).
That said, the presence of virtualization extensions in one's CPU would make a significant positive difference; if the Mac you used lacked VT-x (which could be checked by running "sysctl machdep.cpu.features" and seeing if there's a "VMX" entry somewhere in the output of that), it would certainly explain your difficulties with VMWare and Parallels.
It's also worth mentioning that HyperV isn't exactly equivalent to VMWare Fusion or Parallels; it's more equivalent to VMWare ESXi, Xen, or KVM.