Hacker News new | ask | show | jobs
by zwaps 2749 days ago
Why you would use an Apple computer in actual "production pipelines" that generate revenue, need upgrading, and use external hardware, is beyond me.

In that article we get to read about entire firms using rendering pipelines that are now useless. While that is a terrible blunder by Apple, I really would ask how the responsible parties thought it a good idea to rely on an ecosystem that they have zero control over and that should have been considered "supported" only in an unofficial sense, no matter what Apple says. Heck, the upgrade even breaks older Apple built machines.

Macs and Apple machines are only production machines "as is". And that means they are only made to be interface/user machines. They don't scale, they don't upgrade and they don't work with external hardware. All decisions by Apple - walled garden, the lack of connectivity and the upgrade policy make this ABUNDENTLY CLEAR.

If Apple technology is a node in a pipeline that isn't entirely Apple (or, even then), and those things can not be replaced by other machines immediately, or kept upgrade&update free, then it's your fault.

3 comments

Who the hell upgrades their entire production system to new OS releases without thoroughly testing beforehand? Especially if you're running completely unsupported hardware configurations.

That's just extreme ineptitude at best, grossly negligent at worst.

You just don't do that no matter the OS/hardware vendor - How many people have run afoul of Microsoft releasing broken patches into the wild? If you have mission-critical systems, you test everything in isolation first.

I'm really unhappy that Homebrew twists user's arms to update to the latest version of OSX. I'm glad that I waited a year before I updated to High Sierra, seeing as how there were APFS file corruption bugs, and a default root login bug!

We need to stop being so enamored with Apple, and treat them with the same skepticism as Microsoft.

Several people in my office have been bitten by the Mojave bug and are now regretting it. You should wait at least six months to update OSX.

I'm not sure what you're talking about. I used Homebrew quite successfully this past summer on 10.7.5 - the only problem was that a few formulae weren't available for it. I've since upgraded that machine to El Capitan and Homebrew still works great and I haven't found anything that doesn't work, including CUDA.
I mean seriously. When you had to start to daisy-chain a curious mix of Thunderbold 3 aftermarket applicances, splitters and adapters to your Mac Pro to "set up your pipeline", because Apple has openly, transparently and clearly demonstrated and communicated its periphery usage policy, it should have become clear that what you are doing is VOLATILE.
It's because developer/designer time is worth much more than whatever hardware costs. If you have a great developer on staff and they say they do their best work on OS X, you give them that. If you don't someone else will.
I agree with you if "pipeline" has the narrower meaning I think you're using. In a more general sense, though, I use a Mac all the time in my software dev "pipeline", but I'm much more careful these days to strenuously avoid using anything on the Mac that I couldn't take with me to the next platform (which won't be iOS) once Apple courageously removes enough usefulness from new Macs that I give up and move on.