hikarishadow wrote:
I was saved ONLY because I still had that picture on my iphone. Everyone I spoke to was wonderful and kind. At every step of the process, I pressed how widespread this has become, how many others there were on the forums--several new cases on a daily basis. I was continually told that "things you read on the support forums must be taken with a grain of salt." They do not put much stake into what's written here.
That is why they're losing support from a lot of young tech-savvy developers. They not only strong arm you into buying their products to develop natively for their platform, but they have very little respect for the user. I'm not going to say that I'm an expert at all things related, but as a professional and a lifetime hobbyist in computing, I also expect a certain amount of professionalism in return. With Apple, I get a lot of wordplay to try to make it seem like they've done something dramatic when they've basically regurgitated in Smugspeak (replacing Objective-C soon, guys) what I've just told them. When my girlfriend's 13" MBP's logic board had issues earlier this month, I backed up all of the information in single-user mode, did a ton of diagnostics, and told her it was the logic board and to schedule a repair since she was under warranty. When she went, she told them verbatim what I'd said to tell them the issue was and that it was the logic board. She called me while her computer was in the back to tell me that I was wrong, and that the "Genius" laughed her off and told her that wasn't correct. He claimed it was the battery and some "minor sensory issues" that he'd run some tests on, but that it wasn't anything major. He claimed he'd take it in the back quickly to get a second opinion, but she'd probably be fine with a battery replacement and some other things. I was a bit bothered because I was positive the logic board needed to be replaced.
Minutes later, I got another phone call from her stating that he'd come back and told her that they'd found a major issue and a logic board replacement was necessary. Now, I'm not one to be petty so I was just glad it got fixed, but when we went back to pick it up, I wanted to talk about the repair and how it was covered moving forward. After taking forever to get someone to discuss it, I spent the next few minutes astonished as I heard some very interesting takes on what the logic board was responsible for and its importance. I left there very sour about the level of professionalism that was shown towards us when concerned about a major component of relatively expensive electronics being replaced. It was as if it was blasphemous to even ask what caused the issue and what was done to prevent it happening again. If I were to write code that had a major security flaw in it, I'd be forced to answer to both the people affected and discuss the flaw and methods to fix and prevent further damage.
Accountability is something Apple needs to stress in situations like these because their entire business model with the Mac line is that they're high quality products that always work. With a failed GPU in my MacBook Pro used for personal iOS development and the experience with my girlfriend's logic board, I'm becoming even more disillusioned by Apple than I was before I got the MBP and gained a little respect for its simplicity for things like browsing the web. I'd be more than appeased if I'd just get a little bit of acknowledgement that the issue is indeed being looked into and a solution is en route. Instead, everyone who asks is just being told to ignore that they've seen hundreds others with the same exact problem all around the same time and pay them $500-$700 more to give you back your anomalous Mac.
As said before, get in touch with people and let them know about this situation. Along with the 2011 iMac issue, there is a serious problem with the quality of the hardware that was shipped from Apple in Early/Mid 2011, and it needs to be addressed further than "They have a chance to fail so we'll replace them." I'm not upset because hardware failed because that's the nature of consumer electronics. I'm upset because there is clearly an issue affecting a very specific group of users, and there is neither an acknowledgement of the issue nor is there any method of testing the problem outside of going through Apple to be told the issue. I find it troubling that one of the only tools I was given to try to find a problem said there were not when clearly there is an issue. I'm becoming more and more annoyed by these repeated cases of users going to Apple only to be told that it was their problem, and it'd cost them half a grand or more to get back to normal operations. As someone in the industry, I'm appalled by the accountability and responsibility, both things that software and hardware engineers swear to uphold in the code of ethics as an engineer in this industry, that they've shown for issues or other similar issues, even when they eventually are forced to make the right call. As a customer, I'm upset that I'm without an expensive product until I fork over almost enough money to buy another computer to repair the one I paid a king's ransom for.
What needs to be done is simple. Apple needs to be forced to start being more transparent when dealing with situations that are detrimental to the experience they claim to be dedicated to providing. Whether it be lock buttons on iPhones going limp or GPUs dying, there needs to be an acknowledgement they they're doing their best to solve the problems of the customers and that they will come to a reasonable conclusion based on the situation. For some cases, a flat $310 fee for repair isn't a bad option. In other cases, replacement of hardware may be the only option. Either way, ignoring the problem publicly and telling users that they're out of luck shouldn't be acceptable at all. I'm going to stay as close to this issue and discussion as possible until there is some sort of resolution. I'll also be attempting to reproduce the conditions that cause the issue once my Mac OS X drive has been cloned to another drive to be saved. The more I look into it, the more preventable this issue really was, and someone needs to answers for this.