41–50 of 67 posts
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.
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 is basically the same mentality as putting Ferrari logos on a Fiat Coupé.
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 :)
Earlier quoted context omitted.
Can you describe how you use that with what software packages?
A few examples: using vmware fusion provides an option to enable nested virtualization 1) running a windows vm from macos, and inside that windows vm you enable and use WSL2 or docker desktop. Both of those windows tools require nested virtualization 2) run a hypervisor such as esxi or proxmox as the vm OS, which in turn launches vms. Handy for simulating infra. 3) run a macos vm and inside that vm, install docker de…
Earlier quoted context omitted.
Why would they want to encourage people to buy x86 machines from vendors other than them?
Lure a wider class of people into buying things from the App Store to generate more recurring revenue? Make macOS a more promising alternative to Windows in the corporate space?
Earlier quoted context omitted.
Lure a wider class of people into buying things from the App Store to generate more recurring revenue? Make macOS a more promising alternative to Windows in the corporate space?
Last time I checked it's not like they have excess inventory. And Macs are quite viable in the corporate space - so far, in the past 10 years or so, I have been issued precisely one Windows laptop. All other machines were Macs.
Earlier quoted context omitted.
Last time I checked it's not like they have excess inventory. And Macs are quite viable in the corporate space - so far, in the past 10 years or so, I have been issued precisely one Windows laptop. All other machines were Macs.
Of approx 5,000 employees there are less than 20 Macs at my workplace. We're a Dell/Windows shop with Ubuntu as a popular option for devs. Outside of the tech departments staff usually get generic corporate hardware for light desktop/browser workloads.
Earlier quoted context omitted.
Last time I checked it's not like they have excess inventory. And Macs are quite viable in the corporate space - so far, in the past 10 years or so, I have been issued precisely one Windows laptop. All other machines were Macs.
For tech and art, yes, that's been a solid Apple domain for decades. But your average paper pusher bureaucrat? They get a crap 500$ Dell/HP that constantly has issues because there's no budget for better stuff and 90% of the non-Web/SaaS software in that area is solid Windows-only.
So they wouldn’t buy any macOS licenses unless they are <$50 either? Which makes it totally not worth it and would result in a significant decline in revenue for Apple
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.
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%.
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 :)
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.