Re: *raises snout
I enjoyed your slight against my technical knowledge, but shouldn't you be ironing your turtle-neck for a weekend of Jobs keynote re-runs?
Ah, but I would indeed have time for that if I was partial to turtle necks. If you're running Windows you'll spend that weekend patching, cursing at failed patches, restoring from backup and then trying to stop it from patching again and so end up in the loop of failure that is Microsoft. I'll stop now, I don't want to give Trevor Pott flashbacks :).
If you were running Linux, of course, you'd be in a similar situation to OSX users. The occasional patch and away you go. Occasionally we bounce boxes in the maintenance window to test their recovery and to clean up any dead wood, but it's more luxury than need.
As for slow on fixes, I work a lot with OSX and I have not come across much in the way of exploited zero days. I also known that the Shellshock (bash) bug was dealt with in a few days, but with a patch that actually *worked*. To achieve the latter (patches that do the job) it does indeed take some time, but they get it right most of the time. Could the patches come faster? Sure. Have I experienced any exposure? Nope.
We use OSX because it's quicker to secure and more efficient to use than Windows yet still allows us to use commercial specialist software (servers are Linux). We don't seem to have problems with Yosemite other than that Apple's implementation of webdav seriously sucks, but that has been an issue for longer than just Yosemite.
For the most part, it really just does the job.
Biting the hand that feeds IT
