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

영어가 모국어인 사람들은 왜 한국어를 배우기가 어려운 이유

이 포스트는 내 처음 한국어로 블로그 포스트인데, 한국어에 대하니까 잘 어울린다. =) 자, 시작합시다! 왜 외국사람에게 한국어를 배우기가 어렵다? 난 한국어를 배우고 있는 사람이라서 이 문제에 대해 많이 생각하고 있었다. 여러가지 이유가 있는데 오늘 몇 이유만 논할 것이다. 1. 분명히 한국어 문법은 영어에 비해 너무 많이 다른다. 영어는 “오른쪽으로 분지(分枝)의 언어"라고 하는데 한국어는 “왼쪽으로 분지의 언어"이다. 뜻이 무엇이나요? 예를 보면 이해할 수 있을 것이다. 간단한 문장만 말하면 (외국어를 말하는 남들은 간단한 문장의 수준을 지낼 수가 약간 드물다), 간단한 걸 기억해야 돼: 영어는 “SVO”인데 한국어는 “SOV”이다. “I’m going to school”라고 한국어로는 “저는 학교에 가요"라고 말한다. 영어로 똑바로 번역하면 “I’m school to go”이다. 두 언어 다르는 게 목적어와 동사의 곳을 교환해야 한다. 별로 어렵지 않다. 하지만, 조금 더 어렵게 만들자. “I went to the restaurant that we ate at last week.” 한국어로는 “전 우리 지난 주에 갔던 식당에 또 갔어요"라고 말한다. 영어로 똑바로 번역하면 “I we last week went to restaurant to again went”말이다. 한국어가 왼쪽으로 분지 언어라서 문장 중에 왼쪽으로 확대한다! 이렇게 좀 더 쉽게 볼 수 있다: “전 (우리 지난 주에 갔던 식당)에 또 갔어요”. 주제가 “전"이고 동사가 “갔다"이고 목적어가 “우리 지난 주에 갔던 식당"이다. 영어 문장은 오른쪽으로 확대한다: I (S) went (V) to (the restaurant (that we went to (last week))) (O). 그래서 두 숙어 문장 만들고 싶으면 생각속에서도 순서를 변해야 된다. 2. 첫 째 점이니까 다른 사람을 자기 말을 아라들게 하고 싶으면, 충분히

10 other things South Korea does better than anywhere else

Recently this article about 10 things that South Korea does better than anywhere else  has been making the rounds on social media, but when I first read it, I couldn't tell if it was sincere or satire. A few of the items on the list are not very positive, such as "overworking" and "using credit cards". So, I thought I would try to put together a better list. Here are 10 other things South Korea does better than anywhere else: 1) Small side dishes, a.k.a. " banchan " (반찬) Banchan are by far my favorite aspect of Korean cuisine. Rather than the "appetizer and main dish" approach of the West, a Korean meal is essentially built around small dishes. Even a 5,000 won (about $5 USD) meal at a mall food court will come with two to four banchan in addition to the "main", and often people will actually choose restaurants based  on the banchan (e.g., seolleongtang , or beef bone broth soup, places tend to have the tastiest kimchi). Ther

The King's Speech (and me)

Tonight, I finally gathered the courage to watch The King's Speech . Why did I need courage to watch a movie, you might ask? The reason is both simple and intricately complex: I'm a stutterer (Edit: person who stutters; "stutterer" is not who I am, but something that I do from time to time), and I have been for as long as I remember. Well, there it is - I've said it. To be fair, I actually don't remember stuttering when I was little. My first very distinct memory of stuttering was sometime in seventh grade, when I had trouble saying "nosotros" (we/us) in Spanish class. But I also remember knowing I was going to have trouble saying it, because we were going around the room, and I counted ahead to see what I was going to have to say. Which means by that point I was already stuttering. When did it start? That's a question for another day. So why am I publicizing this fact now? First, I'm in the midst of a lifelong attempt to "cure&quo