4 ms·

Most of the more recent Apple criticism seems to be focused on hardware limitations. People tend to like the OS X GUI and experience for the most part. They jus

Most of the more recent Apple criticism seems to be focused on hardware limitations. People tend to like the OS X GUI and experience for the most part. They just don’t like the Apple hardware you’re limited to now that Macs seem to be less and less of a priority for minor updates. The Mac Pro is literally over years old. The Mac Mini is over two. And the iMac is over a year old as well, besides the limitations of the form factor: it’s a limited machine, and I don’t want to use two monitors after falling in love with a 34” curved ultrawide display. Personally, I came to the same conclusion recently. But I went the Hackintosh route instead of switching to a Linux/dual-booted Windows machine. The latest rMBP’s disappointing hardware and battery life, not to mention the cost premium, made the decision fairly easy for me. That, and I wanted to go back to using a separate desktop and laptop after repeatedly hitting performance bottlenecks with Adobe Lightroom on my previous rMBP. My photography pretty much nixed a Linux option unless I wanted to dual-boot into Windows more often than I’d prefer. There are alternatives like Darktable, but even though Lightroom is a resource pig that needs a diet and a lot of optimization work still, it’s my preferred catalog software that I’m most comfortable in. And when you’re trying to sort through 3-5k+ photos shot over a very busy weekend, comfort is the deciding factor. As a developer, I have no problem with the popular Linux distros. I’ve worked with Linux servers for years, and I love the approach to package management package management. I’m perfectly comfortable with CLI apps. But when I’m not doing dev work, I don’t want to be saddled by the need to constantly boot into Windows for other tasks. The Hackintosh route gave me the best of both worlds. Better hardware that I can upgrade on my own terms, my preferred GUI environment, and no need to dual-boot unless I want to game. I had a bit of extra work to deal with in the beginning to get everything working properly (with my Skylake build, proper audio support and the wireless networking card in particular), but it didn’t take much of an effort thanks to a very robust community ([tonymacx86.com]). The only other issue is checking on discussions for new software updates to make sure there aren’t any problems before I go and install them. But that’s not too big a deal, all things considered. Tl;dr - I guess my point is that we all have our preferred environments and will go to a hell of a lot of trouble to maintain them. Or, if that’s not an option, then to at least get things close to them. Even when that can mean more trouble later on. Using a homebrew port strikes me as a less-than-advantageous approach, but I can imagine why the original author did so.

tambourine_man 10y ago
Does sleeping work reliably with your set up? I heard that was a major pain a few years ago. I would find Kernel Panicing on wake to be unaceptable
- Bluestrike2 10y ago
  Not right now. On wake, the USB peripherals will draw power but the screen stays dark after it receives a signal. It's something I need to look into more, as I recall some Skylake build with the same hardware mentioning that they didn't have sleep/wake problems.
  - djmobley 10y ago
    Assuming you're using Clover, you need to set the darkwake attribute. darkwake=8 worked for me on a Skylake setup (Z170X, Core i5, nvidia graphics card with web drivers). Sleep and wake work flawlessly.
tornadoboy55 10y ago
> And when you’re trying to sort through 3-5k+ photos shot over a very busy weekend, comfort is the deciding factor. From one phtographer to another, and not to be a dick, but if you're shooting that many photos in one weekend you're doing something wrong.. the only scenario where I can imagine reasonably coming up with that many photos is motion photography with burst. Easiest rule I can give you is to pretend you have an old-style camera with a limited amount of rolls. Imagine how many rolls would be reasonable for the session you're having if it was 1980? If you stick to that, your photo quality will dramatically shoot up and the effort you have to expend sifting will go down a lot.
- Bluestrike2 10y ago
  I don't disagree as a general rule. It's good advice, as people tend to go a bit nuts when they discover their camera's drive mode settings. That said, the weekend I was thinking about was about 3-1/2 days of competition. A lot of that was shot in bursts due to the nature of the subject and environment (high motion sports with a lot of movement relative to the sensor plane with crappy lighting and no flash). In that situation, I'm perfectly fine with a low keep rate because I know going in that I'm dealing with a situation that's going to be tough for even modern AF sensors. Doing the same for a wedding reception or something similar would quickly become a bit of a nightmare, though. In my personal work, that's not an issue as I shoot almost exclusively with manual focus glass (Loxia lenses, adapted glass, etc.). With focus magnification and peaking, it's very rare to ever have to reject a photo for blatant focus issues even when I'm using a lens with a razor-thin DOF at f/1.2.

tambourine_man 10y ago

Does sleeping work reliably with your set up? I heard that was a major pain a few years ago. I would find Kernel Panicing on wake to be unaceptable

Bluestrike2 10y ago
Not right now. On wake, the USB peripherals will draw power but the screen stays dark after it receives a signal. It's something I need to look into more, as I recall some Skylake build with the same hardware mentioning that they didn't have sleep/wake problems.
- djmobley 10y ago
  Assuming you're using Clover, you need to set the darkwake attribute. darkwake=8 worked for me on a Skylake setup (Z170X, Core i5, nvidia graphics card with web drivers). Sleep and wake work flawlessly.

tornadoboy55 10y ago

> And when you’re trying to sort through 3-5k+ photos shot over a very busy weekend, comfort is the deciding factor. From one phtographer to another, and not to be a dick, but if you're shooting that many photos in one weekend you're doing something wrong.. the only scenario where I can imagine reasonably coming up with that many photos is motion photography with burst. Easiest rule I can give you is to pretend you have an old-style camera with a limited amount of rolls. Imagine how many rolls would be reasonable for the session you're having if it was 1980? If you stick to that, your photo quality will dramatically shoot up and the effort you have to expend sifting will go down a lot.

Bluestrike2 10y ago
I don't disagree as a general rule. It's good advice, as people tend to go a bit nuts when they discover their camera's drive mode settings. That said, the weekend I was thinking about was about 3-1/2 days of competition. A lot of that was shot in bursts due to the nature of the subject and environment (high motion sports with a lot of movement relative to the sensor plane with crappy lighting and no flash). In that situation, I'm perfectly fine with a low keep rate because I know going in that I'm dealing with a situation that's going to be tough for even modern AF sensors. Doing the same for a wedding reception or something similar would quickly become a bit of a nightmare, though. In my personal work, that's not an issue as I shoot almost exclusively with manual focus glass (Loxia lenses, adapted glass, etc.). With focus magnification and peaking, it's very rare to ever have to reject a photo for blatant focus issues even when I'm using a lens with a razor-thin DOF at f/1.2.