Everything from getting drivers to work, to handling updates, is a major pain. The whole point of the mac is that just works, and a Hackintosh is the furthest possible thing from that.
Why You Should Build a Hackintosh
91–100 of 248 posts
Re: Why You Should Build a Hackintosh
#92Most people invoking a moral imperative to not make hackintoshes are coming from the angle that it’s stealing from Apple. I look at it another way. Apple, as a company is failing to meet the needs of some of its users: - You can’t get an upgradable pro machine - you can’t get a good keyboard (for some definitions of good) - macOS gets more iOS-ified with each release and some people don’t like that Every Hackintosh c…
> I use Linux (and OpenBSD occasionally) these days [...] may be the last un-nerfed general purpose computing platform standing. I really hope you're not right about this, but unfortunately it seems all too likely. Linux will finally win on the desktop not because it finally starts listening to potential users and making things better, but because everyone else just stops making desktops.
Of course those of us on this site are members of the Hacker Class. Putting our own house in order might involve writing code, but meaninful contributions can come in the form of bug reports or even just using software and occasionally writing something about how you use it.
Re: Why You Should Build a Hackintosh
#93Re: Why You Should Build a Hackintosh
#94I'm still using the tower version of Mac Pro with High Sierra and it rocks. I upgraded RAM to 32 GB and the Xeon processors handle everything I throw at them. Opening it and changing drives is a pure pleasure. I really, really don't understand why Apple gave up on these towers and came up with something as inflexible as the current design.
From the beginning... "[Steve Jobs] decreed that the Macintosh would remain perpetually bereft of slots, enclosed in a tightly sealed case, with only the limited expandability of the two serial ports." https://www.folklore.org/StoryView.py?project=Macintosh&stor...
https://www.folklore.org/StoryView.py?project=Macintosh&stor... is the proper URL (for those like me who are curious, and want to see what you're talking about!)
Re: Why You Should Build a Hackintosh
#95I'm still using the tower version of Mac Pro with High Sierra and it rocks. I upgraded RAM to 32 GB and the Xeon processors handle everything I throw at them. Opening it and changing drives is a pure pleasure. I really, really don't understand why Apple gave up on these towers and came up with something as inflexible as the current design.
Re: Why You Should Build a Hackintosh
#96Note: I need High Sierra because I use this particular machine for music production, and the latest Logic Pro X requires High Sierra, and all of my collaborators have updated so I can't open tracks originated by them anymore.
Re: Why You Should Build a Hackintosh
#97Earlier quoted context omitted.
> I don't hate it nearly as much as Windows, and how much Windows is getting worse every release. As much as I try to maintain a fair and balanced point of view, that is a pretty low standard to meet. I work as a sysadmin at a windows shop (~75 clients), and I regularly have to deal with stuff that would make run away screaming if my trusty old GNU/Linux desktop gave me that kind of trouble. Handling updates for Wind…
I wonder start makes your setup so fragile? We have a similar number of Windows machines, and we would be doing nothing in IT this week if we were just answering support calls. We use WSUS for updates, and barely have to touch it? Again I don't have any problem with licensing. I tell a reseller what I want and review their response. No big deal?
So do we. But I have encountered my fair share of cases where an update to Windows or Office broke some third-party application. Once, and update for Office 2007 failed to register properly (but only on two machines), so after the reboot, Windows Update wanted to install that update again, followed by a reboot, etc. Once, an update to Office broke Autodesk Inventor, and reinstalling inventor subsequently broke Outlook. And don't get me started on Siemens SIMATIC/WinCC software. I have seen Office 2013 cease working spontaneously (again, only on a few select machines, and only a full reinstall fixed the issue), I have seen a certain revision of the AV software we use cause Windows 8.1 to crash regularly (literally: every 24 hours, the same time of day).
During my training at a large IT company, I heard they had a team whose entire job was to install and test updates to Windows and third-party applications and test if they broke something. I used to think they were a bunch a wimps, but after a couple of years as a Windows admin, I envy them for having the resources to do that kind of testing. My strategy is to wait for a couple of days after updates become available, check a couple of forums if anybody complains about stuff breaking and then release the updates that I consider safe.
> I tell a reseller what I want and review their response. No big deal?
Have you ever had to deal with, say, per-CPU vs. per-user licensing for SQL Server? Or consider whether to use a plain old license vs. software assurance? Maybe using GNU/Linux or BSD on my private machines has spoiled me, but I always wonder if MS wants to annoy their customers or if they just want to screw them over.
I am not sure if we are doing something wrong or if you are lucky. But I am glad that I do more programming than sysadmin tasks these days.
Re: Why You Should Build a Hackintosh
#98Most people invoking a moral imperative to not make hackintoshes are coming from the angle that it’s stealing from Apple. I look at it another way. Apple, as a company is failing to meet the needs of some of its users: - You can’t get an upgradable pro machine - you can’t get a good keyboard (for some definitions of good) - macOS gets more iOS-ified with each release and some people don’t like that Every Hackintosh c…
My main (additional) consideration: to develop for any Apple platform its required to use MacOS. There is no alternative way for developing and publishing in Apple App Stores.
Re: Why You Should Build a Hackintosh
#99I'm not the Mac Pro customer (just programming) to begin with and I am satisfied with the 2015 and 2018 MacBook Pro's. Just as I don't even have a car let alone need a Lamborghini for groceries.
But it would be nice for once just to step on the pedal of one and hear it roar. If you know what I mean BIG GRIN
I don't think the Mac Pro will ever have USB-A again but surprise me.
Re: Why You Should Build a Hackintosh
#100I moved to a Mac after a decade of Linux on the desktop. After years of fiddling with drivers, crappy trackpad behaviours and so on, I wanted a computer that got out of my way and just worked. MacOS is far from perfect but it works perfectly with Apple hardware. If I wanted to go back to seeing my operating system as a hobby then Linux would be mostly a better option.
The first few months with Linux were fun as I played around and discovered what I could and couldn't do to wreck an install. Zero hardware-related problems.
And then I put multi distros on this generic i-5 box. And left them alone. Zero cares for years. All hardware covered. Xubuntu 18.04 boots from my SSD in under 5 seconds.
I suppose you might have given up at just the time all those problems were going away.
Stick with one of the Ubuntu flavors, or Linux Mint, or MX17, and the likelihood, these days, is that there'll be few problems. Unless, of course, Linux won't run some needed software.