Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by james (1129) on 2006.12.19 13:14 (#52422) Homepage Journal
    I'd actually not had any problems with my MacBook Pro, and was very happy with it. I was referring in the linked blog post to overall failure rates of Apple machines in our office. Of course, two days later the hard drive failed in my own MacBook Pro. All of these things are solved by virtue of Applecare, but there is a significant time overhead.

    As a company it hurts us especially, because we have to negotiate our way through the high level tech support ("have you tried rebooting the machine") when we have already diagnosed the problem for ourselves.

    Apple really needs to provide us with a business level support rather than consumer support. I would conservatively estimate that we are spending 1 man-day a week talking to Apple tech support (which is significant in a company of ~30 people), and we do literally have a pile of broken down PowerBooks, MacBook Pros, and iBooks.

    4 years ago when we started buying Apple machines we didn't have this problem. We moved from an alternate hardware vendor where we had 1 in 4 machines fail to Apple, where it was closer to 1 in 10. Over time the build quality of Apple's hardware has steadily gotten worse and worse.

    While most of us love OS X we are starting to loathe the hardware.