Help me on this. Do people really like say, macOS but not Apple hardware? Is this to lower cost? Just a hobby project?
All the above?
Forgive me. I've been on Linux since the 90s and don't really engage much with the Apple ecosystem. I don't mean this as a dig. I'm really ignorant on this stuff.
- it's expensive, especially if you want to load up on memory or disk space
- there is limited choice
- it's relatively unreliable
- it's difficult to fix, you have to send it to Apple under warranty, third party repairs are difficult or impossible, self fix is impractical for most people
With Hackintoshes you can have a solid desktop machine starting from $150 (motherboard and processor). You can easily fix it yourself by swapping out parts and get local warranty. You can upgrade and downgrade at will. You can use a much wider range of macOS versions.
Laptops are a more complicated issue and much more marginal.
I've used a Hackintosh as my daily driver for about 10 years ever since I had the misfortune of trying to get my brand new MacBook fixed by a "genius" who was actually a rude, condescending arsehole who spoke nonsense. Apple applied the trivial fix of a replacement internal cable and then held my laptop for nearly a week as a matter of policy.
In my case (and I suspect many others) the answer is Xcode. I develop native apps which means I need access to an iOS dev environment. iOS development is nearly impossible without Xcode, so the only way to do it is either pay a virtualization penalty (which is not appealing when Xcode builds already take a massive amount of time), have a specific machine just for iOS work (which would be super inconvenient, even with a virtual KVM), use a Hackintosh (which have problems), or pay Apples exorbitant fees for hardware.
I dream of a day when I can daily drive Linux and also do dev on iOS, but currently that’s not really possible without some unacceptable compromise. I’ve done quite a bit of research and have yet to find a viable solution (recommendations welcome).
I ran a Hackintosh as my main computer between 2014 and 2022. Large part of the reason was cost: I was a student, so I didn't really have money to drop thousands upon thousands to get a Mac desktop. Even dropping like 1200€ on the cheapest MacBook Pro, which got me into using macOS in the first place, was a tough ask.
Another aspect was that the Mac desktop lineup wasn't great. There was the Mac Mini, which had a pretty limited chassis for any kind of expansion, not the best CPU options and ran on integrated graphics. Then there was the iMac, which had the same CPU I chose for my Hackintosh, but was significantly more expensive and came with a monitor that I didn't really need since I already had a good monitor. And lastly there was the Mac Pro, which was overkill both for budget and power, since it wasn't like you could spec it out with an i7 instead of a Xeon. The latest Mac Pro was also the trashcan, really emphasising how not great the lineup was.
With a Hackintosh, I could really just choose what parts I wanted, as long as macOS supported them in some way, and stuff as many SSDs and HDDs as I required over time, since it's not like my student budget expanded to having a separate NAS. And it'd be much cheaper than a comparable Mac, not that there were really any directly comparable ones. Performance-wise the iMac would've probably been the best one.
While it was a pretty superb system, especially for the money, it did get a bit tiresome to deal with the hacky nature of the system by the end of it. macOS updates would always be somewhere between "mild pain" and "large pain", so I did defer updates quite a lot. Sleep also stopped working at some point, so I often kept the computer running 24/7. And when Apple switched over to ARM, I knew that it was time to jump the Hackintosh ship. Thankfully by 2022, I had access to engineering bucks and had already acquired a NAS for my data storage needs, so I replaced my Hackintosh with the first-generation Mac Studio. A lot more expensive than my Hackintosh was, but a great computer nonetheless. Also dropped my apartment's total power usage by like 15-20%.
I've had a Hacktintosh from 2016 until end of last year.
Initially I just did it because I assembled a pretty good PC for gaming, but for work stuff I liked macOS more, so dual booting was a nice option!
This was also before the M-series chips, where you had to pay a hefty premium to get better Intel processors, and also (imo) Apple increasingly struggled with the heat produced by the chips.
Things got a bit more annoying a couple years later, when Apple had their fallout with NVIDIA and would not sign their drivers anymore, which meant I had to buy a cheap AMD GPU to use for macOS.
End of last year I changed a couple of components, including the GPU, in my PC and then decided the hassle with two GPUs was just not worth it for me anymore; so I bought a Mac studio.
I gained some and lost some with this transition. I'm no longer worried about major software updates, it's nice that I don't have to deal with complicated config files for the bootloader every once in a while, and of course there were some minor bugs too.
But I kind of miss the convenience of dual booting, with shared IO and drives. Now I need a network switch, USB-hub and have to toggle between monitor inputs. So yeah! Wasn't all bad!
Anyways, I think it's very cool that there is this community of people that write and maintain special bootloaders and drivers to make it all possible!
I never really understood it either. And I'm someone who (only moderately successfully) used to run Linux on various Mac laptops. I had the opposite problem: I really really really liked Mac hardware, but was kinda meh on the OS.
I think in the mid-00s I could understand Hackintosh users to some extent. Mac hardware was (and still is) expensive, and OS X was a really nice, developer-friendly OS. But macOS has gotten more and more annoying and (IMO) developer-/power-user-hostile with every release. On the rare occasions I have to touch a Mac laptop these days, I find myself getting easily frustrated.
I think for the most part the reasons today are still due to cost. And maybe a little bit of the hacker spirit, just proving that something is possible. I would never use it, but if some folks' ideal is macOS on non-Apple hardware, and can make it work to their satisfaction, more power to them.
I had to unwillingly sell my m1 MacBook Pro months ago because finding work has been a struggle and it came down to selling anything of value.
The only compute I had after that was an old thinkpad x270, dual core with 8gb memory.
I ran Debian with kde for awhile, but I like the macOS workflows and key bindings too much. I like the quality polished native apps folks build. I like homebrew casks, etc. It’s running opencore and Sonoma right now. For me, it was a way to get the OS I am productive in while no longer being able to afford the expensive hardware.
I fear that with Apple making their own arm chips now, hackintoshes are on numbered days. It’s only a matter of time before the OS no longer runs on x86_64 and they are already starting to drop support here and there.
Happy you are posting about hackintosh but generally sharing EFI folders isn’t at all best practice. Anyone who runs a hackintosh should learn how to build a proper config.plist with propertree for their own setup. Spread knowledge not scripts :)
Then OP would have 90% of their Github issues queue consist of "can't get XYZ to work" that's because something in the plist is broken and troubleshooting that can get very painful and annoying.
I would say that after a decade of hackintoshing, an EFI folder for a specific piece of hardware I happen to have is a good shortcut compared to reading tutorials with wildly varying quality of writing, language, and, crucially, information, most of which just describe where you need to go and get ready-made pieces and put them into predetermined locations. In 90% cases, "this tutorial should have been a script".
The reason is twofold. First, tutorials are not "knowledge". They help you to get started, and then... You're on your own. Secondly, most hackintosh tutorials are not even that. Lots and lots of them are written by people who don't really know what they are doing and why. They put something together, they don't know how it works, but they rush to educate the masses nonetheless.
Mechanistically putting the exact bits of configuration into a file and stringing some files in a directory does not make you magically learn how any of this works.
Then again, I'm no CodeRush or usr-sse2 or vit9696 any other hackintosh star, but I've been tinkering with hackintoshes since 2009 and know a thing or two about how they work. However, I'm emphatically not fond of having to rediscover ACPI quirks of my machine on my own if someone else has done it, and done it better.
Once the thing boots and works at its best, I promptly forget all the bootloader and ACPI intricacies I needed to juggle to make it work, this is not how I do my computering. Which is why premade EFI directories are good IMO, once you know what they are made of and why. Bonus points if well-commented .dsl files are published next to .amls, of course.
Since OSX-KVM is out, though, I very happily confine my hackintoshing to a VM if I need it. With VFIO, you can even have accelerated desktop if it's what you fancy.
I'm confused, why are EFI folders unique in their need to be manually pieced together, as compared to pretty much any other of the thousands of subsystems on a computer?
I have used this EFI folder for my own HP Pavilion Aero 13! It works for the most part! I even commented in some of the issues for that GitHub repo a few months back… However, I had issues with sleep/wake. This has been the common pain point for me when working with Hackintoshes. There are a lot of things that can break sleep/wake, and I rely heavily on that feature working without issue.
As much as I love Hackintoshes, they can be a huge time sink if you want 1-1 feature parity with an equivalent Apple product. It is not too difficult getting Hackintoshes to install and boot to the desktop in this day and age thanks to Dortania’s OpenCore guide and contributions from groups like Acidanthera. However, it takes far more time, effort, research, and trial-and-error to get small things working because there are so many different variants and situations to account for. Examples - Wifi/BT and Continuity features require cards pulled directly from a recent MacBook, or a Fenvi card, both of which no longer work with Sonoma without using OCLP / CPU profiles might need adjustment to account for battery life and performance issues / Intel SST was never used with MacOS devices, so any computers using Ice Lake Intel CPUs and Intel SST can’t have a working built-in microphone or headphone jack, etc. Reliability is a pain as well. Anything can break at any time.
At this point, I’ve come to learn that if you want a macOS device that just works, you are better off just getting a new Mac mini (desktop) or MacBook Air/Pro (laptop). I understand the arguments against this (high costs for specs, lack of repairability, intentional sabotage of repairs with third-party parts, used market is a gamble with ADE/MDM and iCloud locks, lack of customization with other computer components, etc). But I (fortunately) have never had issues with any of my MacBooks or Mac minis. And they have always “just worked” for my use cases.
Hackintoshes make for great fun projects where you do not rely on that computer for day-to-day operations. Though the ability to Hackintosh may soon be impossible with newer OS versions. It is only a matter of time since Apple is moving away from Intel x86 processors, which is part of what allowed Hackintoshes to be possible in the first place.
> As much as I love Hackintoshes, they can be a huge time sink if you want 1-1 feature parity with an equivalent Apple product.
Although this is broadly true it can generally be avoided by using proven hardware and premade EFI folders, which is what I've always done. I have no interest in spending time getting things working but there are many options available that don't require it. Most people in this boat are those with existing hardware who are determined to get it working.
> Hackintoshes make for great fun projects where you do not rely on that computer for day-to-day operations.
I run my Hackintosh 24/7 and it stays up for months on end. I've had very few unprompted crashes over the years. The reliability of the hardware is entirely based on what you buy.
> Though the ability to Hackintosh may soon be impossible with newer OS versions. It is only a matter of time since Apple is moving away from Intel x86 processors, which is part of what allowed Hackintoshes to be possible in the first place.
The Intel transition will have little effect on Hackintohses for now. Apple is likely to support their Intel products with updates until about 2030 and then you can keep using them for many years thereafter. Most people will be fine for at least 10 years.
I wish someone would be successful building a Hackintosh of one of the convertibles (or tablets) with Wacom EMR.
It kills me that Microsoft crippled styluses in Fall Creator's Update, and it annoys me to no end having to toggle Settings to allow my stylus to work in Macromedia Freehand (though yes, I'll admit that's better than having to run it in a penalty box).
Every Christmas break I always hope I'll have the emotional energy to dig back into https://github.com/PureDarwin/PureDarwin#readme and see if I can get it to boot, even on VirtualBox, let alone some hackintosh friendly hardware like OP did
I am super, super cognizant that the devil's in the proverbial details, but they sure do seem to publish a lot of macOS into the open <https://github.com/apple-oss-distributions/distribution-macO...> so my interest is to map out the parts that are missing
I'm also aware that Darling exists (e.g. https://news.ycombinator.com/item?id=38423469 ) but if it's anything like Wine -- no, thank you. The only reason Wine (and their CrossOver friends) are required to exist is because there's no suitable open source release of Windows, so emulating the bugs is glucose cheaper. I had high hopes for ReactOS when I was in college, but I think they're just pushing that rock uphill (although I am super glad the project exists)
Having said all of that, don't overlook that even if I snapped my fingers and had a PureDarwin built 14.3 .iso this very second, the supply chain for x86_64 applications for any such OS is likely going the way of the dodo, since it won't be in a vendor's best interest to dedicate resources to building releases for what they assume is a dead platform
As someone who uses macOS for 11 years as the daily driver for his work, I can just say that it would be a bloodbath.
Not only is the driver support abysmal, kext are gone, and the actual quality of macOS has declined significantly over the years.
10 years ago, there was the rule of thumb to wait one update before you do the “big” OS upgrade, now it's better to wait for 3–4 updates as Sanoma crashes on our working machines (1500 people company) frequently.
Speaking of crashes, my m1 MacBook Pro 13, still running Ventura, has crashed more than ANY OTHER mac before. And I'm talking about crashes like, you close the lid, drive to the airport, take a seat, open the lid and just see that macOS starts completely fresh and presents you with a system crash message.
And this is the first Mac where I don't use any kext, strange tools, and completely abandoned software development…
The only thing that let me keep the m1 is the battery life...
kristopolous|2 years ago
All the above?
Forgive me. I've been on Linux since the 90s and don't really engage much with the Apple ecosystem. I don't mean this as a dig. I'm really ignorant on this stuff.
dkjaudyeqooe|2 years ago
- it's expensive, especially if you want to load up on memory or disk space
- there is limited choice
- it's relatively unreliable
- it's difficult to fix, you have to send it to Apple under warranty, third party repairs are difficult or impossible, self fix is impractical for most people
With Hackintoshes you can have a solid desktop machine starting from $150 (motherboard and processor). You can easily fix it yourself by swapping out parts and get local warranty. You can upgrade and downgrade at will. You can use a much wider range of macOS versions.
Laptops are a more complicated issue and much more marginal.
I've used a Hackintosh as my daily driver for about 10 years ever since I had the misfortune of trying to get my brand new MacBook fixed by a "genius" who was actually a rude, condescending arsehole who spoke nonsense. Apple applied the trivial fix of a replacement internal cable and then held my laptop for nearly a week as a matter of policy.
jspizziri|2 years ago
I dream of a day when I can daily drive Linux and also do dev on iOS, but currently that’s not really possible without some unacceptable compromise. I’ve done quite a bit of research and have yet to find a viable solution (recommendations welcome).
Hamuko|2 years ago
Another aspect was that the Mac desktop lineup wasn't great. There was the Mac Mini, which had a pretty limited chassis for any kind of expansion, not the best CPU options and ran on integrated graphics. Then there was the iMac, which had the same CPU I chose for my Hackintosh, but was significantly more expensive and came with a monitor that I didn't really need since I already had a good monitor. And lastly there was the Mac Pro, which was overkill both for budget and power, since it wasn't like you could spec it out with an i7 instead of a Xeon. The latest Mac Pro was also the trashcan, really emphasising how not great the lineup was.
With a Hackintosh, I could really just choose what parts I wanted, as long as macOS supported them in some way, and stuff as many SSDs and HDDs as I required over time, since it's not like my student budget expanded to having a separate NAS. And it'd be much cheaper than a comparable Mac, not that there were really any directly comparable ones. Performance-wise the iMac would've probably been the best one.
While it was a pretty superb system, especially for the money, it did get a bit tiresome to deal with the hacky nature of the system by the end of it. macOS updates would always be somewhere between "mild pain" and "large pain", so I did defer updates quite a lot. Sleep also stopped working at some point, so I often kept the computer running 24/7. And when Apple switched over to ARM, I knew that it was time to jump the Hackintosh ship. Thankfully by 2022, I had access to engineering bucks and had already acquired a NAS for my data storage needs, so I replaced my Hackintosh with the first-generation Mac Studio. A lot more expensive than my Hackintosh was, but a great computer nonetheless. Also dropped my apartment's total power usage by like 15-20%.
Yaina|2 years ago
Initially I just did it because I assembled a pretty good PC for gaming, but for work stuff I liked macOS more, so dual booting was a nice option!
This was also before the M-series chips, where you had to pay a hefty premium to get better Intel processors, and also (imo) Apple increasingly struggled with the heat produced by the chips.
Things got a bit more annoying a couple years later, when Apple had their fallout with NVIDIA and would not sign their drivers anymore, which meant I had to buy a cheap AMD GPU to use for macOS.
End of last year I changed a couple of components, including the GPU, in my PC and then decided the hassle with two GPUs was just not worth it for me anymore; so I bought a Mac studio.
I gained some and lost some with this transition. I'm no longer worried about major software updates, it's nice that I don't have to deal with complicated config files for the bootloader every once in a while, and of course there were some minor bugs too.
But I kind of miss the convenience of dual booting, with shared IO and drives. Now I need a network switch, USB-hub and have to toggle between monitor inputs. So yeah! Wasn't all bad!
Anyways, I think it's very cool that there is this community of people that write and maintain special bootloaders and drivers to make it all possible!
kelnos|2 years ago
I think in the mid-00s I could understand Hackintosh users to some extent. Mac hardware was (and still is) expensive, and OS X was a really nice, developer-friendly OS. But macOS has gotten more and more annoying and (IMO) developer-/power-user-hostile with every release. On the rare occasions I have to touch a Mac laptop these days, I find myself getting easily frustrated.
I think for the most part the reasons today are still due to cost. And maybe a little bit of the hacker spirit, just proving that something is possible. I would never use it, but if some folks' ideal is macOS on non-Apple hardware, and can make it work to their satisfaction, more power to them.
wutwutwat|2 years ago
The only compute I had after that was an old thinkpad x270, dual core with 8gb memory.
I ran Debian with kde for awhile, but I like the macOS workflows and key bindings too much. I like the quality polished native apps folks build. I like homebrew casks, etc. It’s running opencore and Sonoma right now. For me, it was a way to get the OS I am productive in while no longer being able to afford the expensive hardware.
I fear that with Apple making their own arm chips now, hackintoshes are on numbered days. It’s only a matter of time before the OS no longer runs on x86_64 and they are already starting to drop support here and there.
refurb|2 years ago
pjmlp|2 years ago
486sx33|2 years ago
mschuster91|2 years ago
this_xor_that|2 years ago
WesolyKubeczek|2 years ago
The reason is twofold. First, tutorials are not "knowledge". They help you to get started, and then... You're on your own. Secondly, most hackintosh tutorials are not even that. Lots and lots of them are written by people who don't really know what they are doing and why. They put something together, they don't know how it works, but they rush to educate the masses nonetheless.
Mechanistically putting the exact bits of configuration into a file and stringing some files in a directory does not make you magically learn how any of this works.
Then again, I'm no CodeRush or usr-sse2 or vit9696 any other hackintosh star, but I've been tinkering with hackintoshes since 2009 and know a thing or two about how they work. However, I'm emphatically not fond of having to rediscover ACPI quirks of my machine on my own if someone else has done it, and done it better.
Once the thing boots and works at its best, I promptly forget all the bootloader and ACPI intricacies I needed to juggle to make it work, this is not how I do my computering. Which is why premade EFI directories are good IMO, once you know what they are made of and why. Bonus points if well-commented .dsl files are published next to .amls, of course.
Since OSX-KVM is out, though, I very happily confine my hackintoshing to a VM if I need it. With VFIO, you can even have accelerated desktop if it's what you fancy.
colordrops|2 years ago
alarsama|2 years ago
As much as I love Hackintoshes, they can be a huge time sink if you want 1-1 feature parity with an equivalent Apple product. It is not too difficult getting Hackintoshes to install and boot to the desktop in this day and age thanks to Dortania’s OpenCore guide and contributions from groups like Acidanthera. However, it takes far more time, effort, research, and trial-and-error to get small things working because there are so many different variants and situations to account for. Examples - Wifi/BT and Continuity features require cards pulled directly from a recent MacBook, or a Fenvi card, both of which no longer work with Sonoma without using OCLP / CPU profiles might need adjustment to account for battery life and performance issues / Intel SST was never used with MacOS devices, so any computers using Ice Lake Intel CPUs and Intel SST can’t have a working built-in microphone or headphone jack, etc. Reliability is a pain as well. Anything can break at any time.
At this point, I’ve come to learn that if you want a macOS device that just works, you are better off just getting a new Mac mini (desktop) or MacBook Air/Pro (laptop). I understand the arguments against this (high costs for specs, lack of repairability, intentional sabotage of repairs with third-party parts, used market is a gamble with ADE/MDM and iCloud locks, lack of customization with other computer components, etc). But I (fortunately) have never had issues with any of my MacBooks or Mac minis. And they have always “just worked” for my use cases.
Hackintoshes make for great fun projects where you do not rely on that computer for day-to-day operations. Though the ability to Hackintosh may soon be impossible with newer OS versions. It is only a matter of time since Apple is moving away from Intel x86 processors, which is part of what allowed Hackintoshes to be possible in the first place.
dkjaudyeqooe|2 years ago
Although this is broadly true it can generally be avoided by using proven hardware and premade EFI folders, which is what I've always done. I have no interest in spending time getting things working but there are many options available that don't require it. Most people in this boat are those with existing hardware who are determined to get it working.
> Hackintoshes make for great fun projects where you do not rely on that computer for day-to-day operations.
I run my Hackintosh 24/7 and it stays up for months on end. I've had very few unprompted crashes over the years. The reliability of the hardware is entirely based on what you buy.
> Though the ability to Hackintosh may soon be impossible with newer OS versions. It is only a matter of time since Apple is moving away from Intel x86 processors, which is part of what allowed Hackintoshes to be possible in the first place.
The Intel transition will have little effect on Hackintohses for now. Apple is likely to support their Intel products with updates until about 2030 and then you can keep using them for many years thereafter. Most people will be fine for at least 10 years.
tracker1|2 years ago
Wound up back in windows for a bit and now have been on Linux for a few years. Much happier just running Linux at this point.
I'm not sure how much longer it will be before Apple kills off x86 support altogether and a modern hackintosh is simply no longer an option.
WillAdams|2 years ago
It kills me that Microsoft crippled styluses in Fall Creator's Update, and it annoys me to no end having to toggle Settings to allow my stylus to work in Macromedia Freehand (though yes, I'll admit that's better than having to run it in a penalty box).
RecycledEle|2 years ago
I would love to see it compete with Microsoft Windows.
mdaniel|2 years ago
I am super, super cognizant that the devil's in the proverbial details, but they sure do seem to publish a lot of macOS into the open <https://github.com/apple-oss-distributions/distribution-macO...> so my interest is to map out the parts that are missing
I'm also aware that Darling exists (e.g. https://news.ycombinator.com/item?id=38423469 ) but if it's anything like Wine -- no, thank you. The only reason Wine (and their CrossOver friends) are required to exist is because there's no suitable open source release of Windows, so emulating the bugs is glucose cheaper. I had high hopes for ReactOS when I was in college, but I think they're just pushing that rock uphill (although I am super glad the project exists)
Having said all of that, don't overlook that even if I snapped my fingers and had a PureDarwin built 14.3 .iso this very second, the supply chain for x86_64 applications for any such OS is likely going the way of the dodo, since it won't be in a vendor's best interest to dedicate resources to building releases for what they assume is a dead platform
zx8080|2 years ago
Apple is not very frequent in self-shooting in the foot.
OnlyMortal|2 years ago
Microsoft is a software company that builds some hardware.
They’re coming from opposite directions.
dmitrygr|2 years ago
cHaOs667|2 years ago
Not only is the driver support abysmal, kext are gone, and the actual quality of macOS has declined significantly over the years.
10 years ago, there was the rule of thumb to wait one update before you do the “big” OS upgrade, now it's better to wait for 3–4 updates as Sanoma crashes on our working machines (1500 people company) frequently.
Speaking of crashes, my m1 MacBook Pro 13, still running Ventura, has crashed more than ANY OTHER mac before. And I'm talking about crashes like, you close the lid, drive to the airport, take a seat, open the lid and just see that macOS starts completely fresh and presents you with a system crash message.
And this is the first Mac where I don't use any kext, strange tools, and completely abandoned software development…
The only thing that let me keep the m1 is the battery life...
wk_end|2 years ago
WesolyKubeczek|2 years ago
They tried to do such a thing with IBM back in 1995-96. Didn't work out.
mouse_|2 years ago