Just for the record - to benefit people that may read this thread, which is all I care about, not some blowhard stroking his ego and barely-desguised Apple fanboi bias- the original question posed was answered. Building some wanna-be copy of a MacPro using Xeon CPU and server-grade hardware IS possible, and fairly easy to accomplish. It's rarely cost-effective as the MacPro is actually a good deal for what it offers. (IE: You can't even get the two 6 core CPUs in the dual MP for the same cost as the entire MP from Apple.) If you need an actual MacPro, get a MacPro.
Beyond that, it's rarely necessarily, as most people, even working pros, don't actually require the dual MP performance, and the single MP performance can easily be surpassed by consumer hardware. (The current single processor MP as of this writing isn't all that hot of a machine, despite any hype otherwise by people blinded by CPU product names and 'server hardware' and such.)
Someone who desires a Hackintosh to do critcal work with can do so with excellent results- I have for the past 4 years now with no regrets. Every day I'm thankful I didn't waste more money on a MacPro which now would be outdated and much slower than my current hardware.
It's misleading though to suggest in every case that one constantly has to deal with system support and maintenance, instability, or rely on hacked and patched drivers. . For the record- this doesn't have to be the experience at all if you stick with tried and tested hardware. The goal is to be as native as possible, if not 100% native, and you can easily achieve this by using hardware that has full support.
One has to understand that actual Mac hardware isn't anything all that special. Apple doesn't make any of it themselves- they use commissioned motherboards from Foxconn, chipsets and CPU from Intel, graphics from ATI, nVidia or Intel, etc. etc. All the crucial components like audio, networking, I/O and such are all third party. The best Hackintoshes simply have the right combination of the exact same components Apple uses, and therefore for which drivers already exist. So one doesn't need to rely solely on the OSx86 community for support with these since native support exists, rather just for information on how best to set things up.
If a person wants to build a Hack for work, they need to understand this. Right now, if one wants to build an IvyBridge system for example, then yes, you're going to be relying on community support, because Apple has only just started to build in native support, as most current Macs aren't yet IvyBridge. But one can easily build a Sandybridge system where every component has a natively supported driver. (Eventually, IvyBridge will have this too).
If you're the type that typically has never relied heavily on tech support for your computers, you can read and follow instructions, aren't a know-it-all wanker, and doesn't run to Geek Squad or Apple Care every time something needs to be figured out, then you can easily build and maintain a Hackintosh and use it for critical work. If you're the type that can't fathom cracking a case, has a bias toward DIY because you believe the magic Apple fairies watch over the same hardware branded by someone else, and break out in a sweat without being under a full warranty by whoever made your computer (and definitely if you're a shill for one box-maker or another) then you should stay far, far away from Hackintoshing.
ZaapMember Since 22 May 2008
Offline Last Active Jan 24 2014 06:32 AM
- Group Members
- Active Posts 681
- Profile Views 1,596
- Member Title InsanelyMac Legend
- Age Age Unknown
- Birthday Birthday Unknown