I tried once but now I don't understand it. The main benefit for me using OSx is that is a nix desktop os that works well on a very specific hardware. Having used linux on the desktop before for years I always had some problem with drivers and alike. If I were willing to deal with these kind of issues I'd do it with some linux distribution not osx. I guess there are some cases like developing software for Apple os.
Building a CustoMac: Buyer's Guide
41–50 of 99 posts
Re: Building a CustoMac: Buyer's Guide
#42Earlier quoted context omitted.
I'd argue the point of giving the OS away for free was nothing to do with buying new devices. It was probably to make sure people upgraded sooner, rather than being put off by having to buy the new version. Better for the whole ecosystem.
Well put. Its just like iOS--developers are happier if most people are running the latest version. Less version-fragmentation. The "less adopted" variants of Windows are a problem for development and testing. It might make sense to only support/test XP, 7, and 10--but what a mess that is.
Re: Building a CustoMac: Buyer's Guide
#43I tried once but now I don't understand it. The main benefit for me using OSx is that is a nix desktop os that works well on a very specific hardware. Having used linux on the desktop before for years I always had some problem with drivers and alike. If I were willing to deal with these kind of issues I'd do it with some linux distribution not osx. I guess there are some cases like developing software for Apple os.
I just want to run OSX in a VM.
Re: Building a CustoMac: Buyer's Guide
#44Earlier quoted context omitted.
I'd argue the point of giving the OS away for free was nothing to do with buying new devices. It was probably to make sure people upgraded sooner, rather than being put off by having to buy the new version. Better for the whole ecosystem.
Well put. Its just like iOS--developers are happier if most people are running the latest version. Less version-fragmentation. The "less adopted" variants of Windows are a problem for development and testing. It might make sense to only support/test XP, 7, and 10--but what a mess that is.
Re: Building a CustoMac: Buyer's Guide
#45Re: Building a CustoMac: Buyer's Guide
#46While I'm not saying it's not fun to try and run OS X on PC hardware, can anyone explain to me how this is not morally equivalent to unauthorized copying / software piracy, given that they are both violations of the license agreement?
If you acquired the software legally, what then do you think? Now ask yourself this question if you legally purchased Oracle or MSSQL, and were evaluating for an application, testing, etc - and now I inform you that that's unauthorized, and Oracle's license forbids you from doing any form of benchmarking related to the database. Do you feel that you are being immoral to test your application?
To me what they are doing are no different from the people distributing cracked games with disabled copy protection.
Re: Building a CustoMac: Buyer's Guide
#47Earlier quoted context omitted.
> and for older hardware makes sure to let you know that your Mac/iOS device doesn't support this feature. Where is this case? In my experience, something I saw online simply wasn't available to me, like AirDrop, for instance. I upgraded my mid-09 MBP to 10.7, looked for AirDrop and couldn't find it. Same for Handoff and the Bluetooth-required new features in Yosemite. Apple doesn't go out of its way to inform me my…
Re Handoff in Yosemite... there are hacked kexts that make it work just fine in older (non BT LE/4) Macs (with regular BT) making it fairly clear that an artificial limitation was introduced.
Given that, it makes me wonder how the unmodified Mac mini and MBA perform.
Re: Building a CustoMac: Buyer's Guide
#48Earlier quoted context omitted.
Once it's set up and working the way you want, how often do you find yourself dealing with small issues?
Not the OP, but I built one based on one of these guides 2 years ago. The only problem I have is that once in a while (1-2 a month) the sound doesn't work after resuming from sleep. I have to reboot to get it back. Otherwise I don't have any issues. I'm running the latest Mavericks, could install updates etc.
I have a 2013(?) Mac Mini that was running Lion (and then Mavericks) and it did the same thing with HDMI audio on every single unsuspend. It took months for an update to come out that finally fixed it. Not saying your problem isn't due to hackintoshing, but getting the real thing (since 2005 and the first mac mini, for me) hasn't been problem-free either.
Re: Building a CustoMac: Buyer's Guide
#49Re: Building a CustoMac: Buyer's Guide
#50Earlier quoted context omitted.
> What's 'real' about the 'real' Mac Mini that's not real about this one? Warranty and support. If Apple releases an update that breaks your Hackintosh then too bad, if Apple does it to your $100 more legit Mac Mini then you can moan at them if nothing else. I do, however, completely agree with the upgrade argument. Particularly with the latest gen' of Mac Mini which don't allow the RAM to be upgraded because greed.
If your definition of support is the ability to "moan at [the vendor] if nothing else", is it really worthwhile to consider as an alternative? Your hardware is still warrantied by the respective vendors.