Skip to main content

Apple and the Rich Idiot Babies

Apple devices are nice - they're pretty, they're shiny, they seem to be well designed. But then something breaks, and you quickly learn that appearances can be deceiving. It's only when something goes wrong that you truly learn how a company feels about their customers.

Take Zappos, for instance. Their customer service is famously good. I've experienced it firsthand, and it left me feeling like Zappos cared about me as a customer and treated me like a respected adult.

Apple, on the other hand, takes what I like to call the "rich idiot baby" approach to their customers. The operating system is designed from the ground up with kid gloves - e.g., why would you ever need to know where on your hard drive a file is actually located? Leave that to Dad to worry about. But for the most part it's still a usable OS, and since I do some iOS development, I decided that "the real thing" was the way to go.

Inevitably, sooner or later, something goes wrong. In my case, my laptop was probably defective from the moment I carried it out of the store, but I never knew until recently when I got a new monitor. The problem seems to be in the Thunderbolt chip or port itself. When connected to a Thunderbolt display, the display flickers black every minute or so for a split second. You can imagine this being quite annoying, especially given the price of the display. I made sure my software was all up to date, then brought the monitor back in for testing, and sure enough, I'm told the monitor is fine. Great.

Thus begins the yak shaving adventure of trying to fix something on a Mac. Since Apple thinks you are a rich idiot baby, the goal, of course, is to make it as hard as possible to actually diagnose and fix your problem. A bunch of Googling leads me to discover that there is an "Apple Hardware Test" included in the OS. I'm told that it's not very intensive, but will rule out obvious things. I figure it can't hurt, so I follow the instructions to run it (just hold "D" during boot). And ... nothing. Supposedly, it will boot from the Internet "if it's not included in your copy of Lion" (why wouldn't it be??), but instead, my system refuses to enter AHT. Perhaps it's cause I'm out of the United States, or perhaps their support site is out of date. Regardless, no hardware test for me.

No worries, I think. It sounded like a lame test suite anyway. Some more Googling leads me to something called the Apple Service Diagnostic suite. This sounds like what I want. It's an intensive series of hardware tests for diagnosing problems with your Mac. Someone on a forum mentions it's not free, but whatever, I'm willing to pay the $19.99 or whatever it costs on the App Store in order to finally have some real diagnostic tools for my Mac. I find a link to the actual suite on the Apple site, excited that I'm about to get some answers, when the price hits me in the face like a rabid madman swinging wildly with an iPad:

$999

What. The. Fuck. Apple wants to be so absolutely sure that you will need to bring in your Mac for service that they make their diagnostic suite nearly completely inaccessible for consumers. That is how they view their customers - they're not just babies who need everything to be super easy and safe so they don't mess anything up, but they're also idiots who can't think for themselves, and have an unlimited credit card in case they want to solve a problem the Apple way: by buying a new system. I try to get an actual support rep to help me run the lame-ass AHT suite that wouldn't actually start up before, but that would cost $49 for a "single incident" tech support call. Forget it.

The saddest part of all this is that despite still being under hardware warranty, I've probably voided it by upgrading to 16GB of third-party RAM, since having Apple upgrade it at purchase would have cost about six times as much (literally). Sigh. Next time, I think I might go Samsung, simply because I find their "you can't copyright a rectangle" IP defense ballsy and hilarious.

Comments

  1. I got a service response from Apple for an itunes problem. My account was inexplicably blocked/rejected when it was working fine for years up to then.

    The response was that I violated the Terms and Agreement, and they gave me a link to the Terms and Agreement. (Note: again, I hadn't changed anything. I was just trying to download an app.)

    OK. I was totally willing to not do whatever they thought I did.

    However, the punchline is that link went to the Terms and Agreement which was about 50 pages long -- and they didn't say which part or item of the terms and agreement I was in trouble with.

    Basically it was an "FU! Figure it out yourself. Its your fault we changed the terms and you didn't follow along with every line of it."

    Yah, that was the last time I expected any kind of help directly from Apple.

    ReplyDelete
  2. If you don't read the full TOS, you might turn into the human centiPad. Be careful.

    ReplyDelete
  3. My last few broken i-product experiences were pretty good actually. I just took it to the store and within 15 minutes it was either solved or the device was replaced. Having said that, the devices I own are glued shut so there is very little I can do to void warranty.

    I've spent a lot of time fiddling with hardware in my lifetime. I even water-cooled my pc from a bunch of pieces I bought on eBay back in high school days. These days if something breaks on PC I sigh, because I know that on average I'll be syncing 4 hours of my life to diagnosing and fixing the issue. There is also no way around that unless I'm okay giving the PC away to a local store for 48 hours or more.

    It's nice to have the two extreme options and I'll never go all-Apple, but if you get an Apple product then you definitely are stuck playing their game.

    PS. is your monitor an official Apple monitor? :-)

    ReplyDelete

Post a Comment

Popular posts from this blog

English Lesson: "한국에 오신지 얼마나 됐어요?"라고 영어로?

I've lost count of how many times Koreans have asked me the question, "How long do you stay in Korea?" in those words or something very similar. Clearly this question is taught in every English class in Korea, because I hear it over and over again, so I just wanted to be very clear about something here:

DO NOT USE THIS EXPRESSION. IT IS INCORRECT.

This phrase is incorrect for a few reasons, but primarily because it sounds ambiguous to native English speakers. Specifically, there are probably two different questions that you really want to ask:

1) How long have you been in Korea? (한국에 오신지 얼마나 됐어요?)
2) How long will you stay in Korea? (한국에 얼마나 있을 거예요?/한국에 얼마동안 있을 계획이에요?)

Nearly always the intended question is number 1, "How long have you been in Korea?", followed afterwards by number 2, "How long will you stay in Korea?". But the incorrectly stated question ambiguously sounds somewhere in between number 1 and number 2. So, don't ever use it again. T…

Stuttering in Korea

I had given up on English. It's my native language, but I figured after 30 some-odd years of disfluent speech, it was time to try something else. So I signed up for language classes in Korean, rationalizing that if I was going to try to teach myself how to speak, I might as well learn a new language along the way.

This might seem completely insane, but when the prevailing theme of your conscious thoughts for multiple decades is some variant of "Why can't I say what I want to say?", you come up with lots of crazy ideas.

For background, I've been a person who stutters for my entire life. I wrote about it on this blog a few years ago, so I think it's time for a followup. I've learned a lot since then, about myself and about stuttering, but in this post I simply want to give some insight into what it's actually like to stutter, and how my speech has changed over time.

After the last stuttering post, the predominant reaction I got from friends was either &…

Why Korean Is Hard For Native English Speakers

A couple of days ago, as an experiment, I wrote my first blog post ever in a non-English language. It was an attempt to explain some of the reasons that Korean is hard to learn for native English speakers, so I figured I might as well try to write it in Korean. Those of you who actually read Korean can see how awkward the attempt was =).

In any case, the post came from an email conversation I had with The Korean from Ask a Korean, a fantastically well-written blog about all things Korea from the perspective of a Korean who moved to the United States during high school. Since I tend to geek out on language things, I figured I might as well post part of that conversation. An edited version follows.

---------

Out of the languages that I've attempted to learn so far, Korean has been the hardest. I've done a lot of meta thinking about learning Korean, and I think there are a number of reasons it's difficult for non-Koreans (and especially Westerners) to learn:

1) Obviously, the…