Apple: The Bad and the Ugly. And Some Good

by Chris Howard Apr 13, 2006

Apple does some good things. Boot Camp for example. Everyone’s talking about Boot Camp. If I had been writing last week, I too would have been writing about it. In fact I was last Thursday. But I lost that piece. That event lead me to this article

I had been scratching together pieces for this article for a few weeks as the blinders have come off, and I had been noticing lately all the things that Apple and its products don’t do so well.

This came to a head last Friday when my hard disk passed away. I spent the next four days getting my system back to close to what it was. Fortunately I did have backups. Not perfect ones though as I hadn’t done a full backup for two weeks, but I had backed up my critical data the day before. I also learned some lessons about how I should have been doing things (mind you, things with 20 years experience, I already knew and should have been doing.)

In the recovery process, I discovered some things that displeased me to say the least. On top of other recent experiences of little and big grievances I have with Apple’s way, it is time to write about it.

The Bad

  • Apple’s Backup application does not verify the integrity of backups after they are completed. (I know some people don’t like Backup, but I had found it to be the most reliable solution - too many others I tested aborted the backup when they found open files.) The restore function also needs to be able to skip corrupted backup files and give more options on handling replacement of existing files. But I have been kicked in the pants by a lesson I already knew… Check your backups. Do a test restore. Regularly. With Apple’s Backup, you can also show the package contents of the backup file, then drill down to the Contents and in there, open the Backup.sparsimage file. If it fails to open, do a new full backup - even if the failure was in an incremental backup. It would be appreciated greatly if Apple included an option to test a backup file - at least for readability.
  • Backward compatibility of OS X extends only until last week. Ok, maybe to Panther and occasionally to Jaguar. One reason I’ve continually upgraded with each iteration of OS X, is to ensure that all applications will run on my OS. Have a look through the Apple store and see how many applications need Panther or later. For example, the minimum OS requirements for various applications on the Apple Store are: iLife - 10.3.9; iWork 10.3.9; MS Office 10.2.8; The Print Shop - 10.2; Photoshop Elements - 10.3; Final Cut Studio - 10.4.4; The Sims 2 - 10.3.8; Quicken 2006 - 10.2.8; Toast 7 - 10.3.9; Logic Express - 10.4.3; Logic Pro - 10.4.3; QuickTime 7 - 10.3.9. Now notice the pattern? Apple is the worst offender. If you want to use Apple’s software, you must upgrade to the latest OS. That last one, Quicktime, is interesting. If you want to run it on a Mac, you’ve got to have an OS released just two years ago. Yet the Windows version will run on the six year old Windows 2000. So it’s all well and good that Apple keeps updating OS X, but at least on Windows, most software will run on OSes more than two or three years old.
  • Finder’s copy doesn’t merge folders. When you copy a folder in Finder, it treats the folder as a single entity, rather than looking at each file within the folder. If you want to merge folders you either have to copy the files for each folder individually; or use XCode’s FileMerge utility (which also lets you merge folders); or find a utility online that will do it - though most will cost you money. I tested this on a Windows computer and XP does merge folders. So if a clapped out system from way back in 2001 can do it, why can’t OS X Tiger from 2005? For the zealots who believe Apple’s is the only way, maybe OS X (being sooo user friendly…) could provide a prompt asking if you want to merge or replace.
  • Again on backward compatibility, iPod users suffer. If you want new features, you buy a new iPod. Apple doesn’t seem to have any interest in providing new features for older iPods. Case in point: Volume limiting. Surely this is a simple firmware upgrade. Even if it doesn’t work the same way as on 5G iPods. 5G iPods have the security function built in so they can be password protected but is that hardware dependent? It shouldn’t be. The same functionality could easily be offered to owners of older iPods. But no, Apple wants you to buy a new one. So everyone is going around saying how great of Apple to introduce Volume Limiting, but there’s half-a-gazillion iPod owners that won’t get that function. There’s possibly more teenagers frying their ears with older iPods than newer ones. Thanks for your kindness Apple.
  • We’re all well aware of how Apple is monopolizing it’s share of the MP3 player and music downloads markets, but it monopolizes its computer market just as much. Whether it’s by forcing upgrades, charging for incremental upgrades, not allowing OS X to run on PCs or not licensing FairPlay, Apple does frustrate with it’s “My way or the highway” attitude.

The Ugly
If I was really cynical about Apple trying to screw more money out of its customers, I would have put the backward compatibility issues under “The Ugly.” It was border line… But I still have a couple of uglies.

  • Apple is a technology company right? Do you reckon it knows anything about software development? Database development? Sales systems? Do you reckon that just maybe, it could link its sales and warranty systems? You see, the hinge broke on my PowerBook that came with a free three-year Apple Protection Plan warranty. Apple won’t honor the warranty unless I, yes I, me, this person typing, can prove that it came with the APP! Excuse me?! In 2003 when I purchased it, Apple had a promotion on whereby purchasers of Macs, who were in government or education, received a free three year APP. This included me. Now wouldn’t you expect that each system sold would have been tagged on Apple’s database as having that deal? No way - Apple doesn’t want you to be able to claim your warranty unless you can prove it. Possibly the reseller may have screwed up by not listing the APP on the invoice, but Apple should still know about that deal and my Mac being bought on it. If I give my serial number, Apple should know everything about the purchase of my machine. Zero for Apple’s customer service.
  • Right at this point in time, I’d find it hard to recommend anyone to buy an iPod because of this and the next point. I bought a 30GB iPod Photo last year to use for backups and to allow me to move data between computers - kind of like a souped up USB key. That’d be fine if I only wanted to transport files between Macs but a Mac formatted iPod will not work on a Windows PC without the iPod being reformatted. And the thing is, to reformat your iPod to work with Windows, you have to use a Windows computer. And then God only knows what will happen next time you plug your iPod into your Mac.
  • From my testing, it appears that iPods carry their iTunes configuration on them. So you can’t change an iPod’s settings without plugging it into your computer. But when you do, it kicks in with its settings. As I found out to my horror, with auto-syncing of iPhoto, it will wipe your photos from your iPod if you plug into a different computer. No questions asked. No prompts. When, like me, you use the “Full Resolution” option so your iPod is your primary backup, and your secondary backup has already failed, how do you think you feel? Very ill to say the least. Dear Apple, No application should ever wipe files without first warning the user and giving them the option to abort. I was on the verge of paying for SubRosaSoft’s FileSalavage or its Sibling, iPodSalvage, until I discovered a third backup of my iPhoto library. You can’t have too many backups! I’ll go into this more when I review Backup.

The Good
Regardless of the disaster that befell me, and the subsequent horror stories, there have been some things I’ve really appreciated about Apple.

  • Despite some failed backups meaning a much more manual restore process, .Mac’s Backup is a good tool. You just have to test those backup’s regularly. I’ll explain in a later article how to get around a failed incremental backup.
  • Sync (in .Mac in System Preferences) is an excellent and simple way to backup and restore your bookmarks, calendars, contacts, keychains and mail settings. If you’ve got .Mac, you should use it as it’s even easier than using Backup for these items. Also for this reason, I will probably switch to using Keychain for saving registration numbers, etc, even though it can be a little cumbersome to use at times.
  • Firewire boot is a Godsend. Fortunately, I had a couple of months ago installed OS X on my external hard drive. So when my internal died on Friday, I simply booted from the external - which I am still operating from. Apple does make a lot of things easy, and this is one of them.

I will post a review of Apple’s Backup in the near future and go into more detail about my experience and about better backup practices, but if any developers of backup solutions are reading this and believe they’ve got a better product, feel free to contact me by email at chrish at this site’s domain.

So those are my issues, but maybe it’s just me. Maybe I’m the only one who’s experienced the bad to ugly side of Apple and Macs…

Comments

  • That makes utterly no sense. What is preventing you from working on your current version of FCP?
    Your old copy does actually still work after a new release comes out, yunno?

    Well, let’s see.  I work with several editors, and since most of them do regular upgrades that means I have to do regular upgrades or, you know, I can’t work, since the upgrades aren’t BACKWARDS COMPATIBLE.

    Get it?

    And in that case, why the heck are you complaining?

    You’re right.  Let’s us forget that there are any issues whatsoever and soak in the warm peaceful glow of the Apple logo.  I’ll bet it’s alot easier than having your own opinions or thinking for yourself.

    Beeblebrox had this to say on Apr 16, 2006 Posts: 2220
  • “the upgrades aren’t BACKWARDS COMPATIBLE.”

    FCP 5 has so many fundamental changes, its whole core is different from FCP 4.
    You’re trying to single out Apple for something that is no different to any other software applications.

    Name me anything similar to FCP that is backwards compatible. It doesn’t have to be on Mac, just any piece of complicated software where the native project files are backwards compatible.

    And before you say, “MS Office”; a word processor isn’t a complicated piece of software (at least where the basic saving and opening of files is concerned.)

    And why can’t you just export a batch list or EDL?

    Luke Mildenhall-Ward had this to say on Apr 16, 2006 Posts: 299
  • First you say I should just be able to work with my current version.  Obviously that’s not the case.  Now your apologist blathering is that “Apple is no different than anyone else.” 

    Really?  That makes all this stuff about Apple being superior kind of a farcical charade, doesn’t it?  It exposes claims such as, Apple are the only ones who have realized you do have to compromise on features for a better experience,” for the empty rhetorical nonsense that they are.

    So is Apple better?  Or are they like everyone else?  Or does that depend on which drooling fanboy excuse you’re making at the time?

    Beeblebrox had this to say on Apr 16, 2006 Posts: 2220
  • Drool fight!

    sjk had this to say on Apr 16, 2006 Posts: 112
  • OK, I’ll take that as meaning you couldn’t think of one then, Beeblebrox wink

    :“First you say I should just be able to work with my current version.  Obviously that’s not the case”

    I gave you a work around already:

    And why can’t you just export a batch list or EDL?

    I’ve had to work on projects circulating between Final Cut Express 2, Adobe Premiere and Avid Xpress Pro. I haven’t been “forced” by Apple to do anything. Maybe you’re just a lightweight?

    Luke Mildenhall-Ward had this to say on Apr 16, 2006 Posts: 299
  • I haven’t been “forced” by Apple to do anything.

    So if that’s the standard, then EVERY complaint ever uttered about just about anything is “nitpicking.”  Having to run a virus-scanner in Windows?  Suck it up.  No one’s holding a gun to your head.

    Chris’s point, and one I agree with, is that if he were making similar complaints about Windows, no one would argue with him, let alone spew out such lame apologist excuses.

    You and Capn Van only serve to prove our points by continuing to toss out these ridiculous and hypocritical defenses of Apple rather than concede a single legitimate complaint.

    And why can’t you just export a batch list or EDL?

    So having to export and re-import batch lists and EDLs just to work between FCP version 5.0.4 and version 5.1 is what you call a work-around so acceptible that complaining about it is “nitpicking.”

    Again, what WOULDN’T you consider nitpicking at this point?  I guess if Macs exploded in people’s faces upon logging on, you’d simply say that “all you have to do is not log on.  Geez, what’s the big deal?  It’s simple…and…it’s supposed to do that…and…blather blather blather.”

    Beeblebrox had this to say on Apr 16, 2006 Posts: 2220
  • Beeblebrox (#36): “So if that’s the standard, then EVERY complaint ever uttered about just about anything is “nitpicking.” Having to run a virus-scanner in Windows?  Suck it up.  No one’s holding a gun to your head.”

    Luke (#29): “What I consider nitpicking are pointing out things that will affect 0.1% of the users. “

    Beeblebrox (#36): “Again, what WOULDN’T you consider nitpicking at this point?  I guess if Macs exploded in people’s faces upon logging on, you’d simply say that ‘all you have to do is not log on.  Geez, what’s the big deal?  It’s simple…and…it’s supposed to do that…and…blather blather blather.’”

    Again, I already answered your question:

    Luke (#29): “What I consider nitpicking are pointing out things that will affect 0.1% of the users. “

    However, I do actually think the upgrade issue is one of the more substantial points brought up. But only the 5.0.4 - 5.1 thing. I know that pissed off a lot of people, and I definitely don’t agree with that. But the examples given by Chris in his article, including where he said, “If you want to use Apple’s software, you must upgrade to the latest OS.” even though, of his list of examples, only 2 -professional- products required the latest OS, with many on the list running on 10.2. Plus the iPod volume issue - those points are unquestionably nit-picking. Why? Because they don’t actually affect Chris personally, he just wanted to add more things to the list. = nitpicking.

    And please stop with your mindless rambling on how I’m an ‘apologist’, or ‘shill’, or ‘drone’; it’s adding nothing into the discussion.

    Luke Mildenhall-Ward had this to say on Apr 16, 2006 Posts: 299
  • And please stop with your mindless rambling on how I’m an ‘apologist’, or ‘shill’, or ‘drone’; it’s adding nothing into the discussion.

    I’m boycotting comments containing pompous lowbrow insults.  In person and online, I quickly lose tolerance for those continued remarks from anyone who’s been politely asked, several times, to cool it.  They just get more disrespectful and offensive coming from someone who’s capable of realizing that.

    sjk had this to say on Apr 16, 2006 Posts: 112
  • At the risk of being labeled an Apple-apologist, here goes:

    First of all, Apple doesn’t deserve all the blame for the upgrade issue. There are thousands of other developers making software that requires the latest version of the OS, too. Sometimes there are reasons a decision like that is made, though. Tiger introduced Core Data and Core Image, along with numerous other API enhancements that offer more options to developers. Sure, it may seem like a lot of Apple’s requirements arbitrarily increase with each OS upgrade, but sometimes it’s because the new version uses functions that weren’t available before.

    As for the iPod issues, you’re losing sight of it’s intended purpose. It’s not meant to be a backup device or a full-featured portable hard drive. It’s supposed to play music and let you look at pictures and videos. Also, it’s a consumer electronic - a market that doesn’t really lend itself to upgrading existing devices. Apple is in the business of selling iPods; when they release new features, they do it because they want you to buy a new one. And besides, if you can’t trust your kids to listen to the iPod at a reasonable volume, maybe you shouldn’t let them have them in the first place.

    The warranty situation sucks. Once again, it’s not Apple’s responsibility to make sure you have proper documenation though. It’s your job to have it, and it’s your reseller’s job to make you they give it to you. Unless you bought it from Apple it’s not really their fault. I know from experience that resellers aren’t always reliable with that stuff (especially campus stores) - in December my reseller told me that my dead iBook wasn’t covered under the Logic Board Repair Program and because I didn’t have the time to waste to get a second opinion from Apple, I ended up buying a new computer. It wasn’t until a month later when I finally had time to get in touch with Apple that I discovered they would have actually fixed the iBook for free. And they were incredible fast and helpful when the ball was finally in their court.

    And finally, when it comes to the merge vs. replace debate, I don’t see what’s so confusing about a dialog box that explicit says it’s going to REPLACE the item (in this case a folder). As has been said before, this is the way Macs have always functioned, and it’s not Apple’s fault that you’re expecting it to work like a different platform. Is it also Apple’s fault that the Home and End keys don’t work the way they do in Windows?

    Joe B. had this to say on Apr 17, 2006 Posts: 4
  • Luke, you got me all wrong! I included that list of software for objectivity. It would have been easy to only include apps on it that supported my theory. But you use my objectivity against me.

    And yes, I also feel you brushed my complaints off with your simple “nitpicking” argument.

    As to nitpicking, it doesn’t matter how many people it affects. One person lost at sea will get as big a search party as ten.
    One person with a gripe has changed the world many times.

    0.1% is a very big number. If 1 in a 1000 plane flights crashed, no one would get on a plane. If 0.1% of Apple customers have the same gripe, that’s tens of thousands of people.

    One of the most dangerous arguments is the majority thinking. “Hey look, dogs crap on the sidewalk/footpath”
    “Gee, no one else has complained, so what are you complaining for?”

    We don’t have to shut up about things that are wrong, even if we’re the only one’s affected. The warranty issue was fine in years past but we have the technology now.

    We complain how much information companies and the government have on us, yet Apple can’t even tell me my computer came with a 3 year warranty.

    Just because the majority haven’t complained, or aren’t aware of an issue, doesn’t make the issue irrelevant.

    Just because you’ve never heard of anyone else making these complaints, doesn’t mean they’re not worth making.

    As a business owner, you look at every opportunity to improve customer service and satisifaction. If a wheel squeaks, oil it. Even if it’s a little squeak.

    As far the file copy goes, Bart hit the nail on the head: copying should never delete.

    Regards reading the dialog, yeah I did read “Replace”. That’s why I went looking for a solution.

    But Apple’s approach is plain WRONG. It does not fit the metaphor of how folder copying is done in the paper based world. I can’t think of any situation where copying (or moving) deletes.

    “Hey can you just move that second pile of bricks over there with the first.”
    A bit later: “Why the hell did you get rid of the first pile of bricks?!!”
    “Well you said to move the second pile, and my Mac would delete the first pile, so that’s what I did.”

    How would you feel if the photocopier deleted your originals? Even if you were only copying 2 of 10 pages. It’s not quite the same, but that’s how ridiculous the Apple way is.

    As I said in an earlier comment, if I gave you a folder to file marked Bill Smith and he already had a folder, would you toss out the existing folder? Or would you add the documents from the second folder to the original?

    No person in their right mind would toss out the original folder.

    But that’s what Apple’s copy folder function does.

    And people are prepared to defend that on the simple grounds that Apple’s OSes have always done it that way.

    Chris Howard had this to say on Apr 17, 2006 Posts: 1209
  • OK Chris. You have defended yourself quite well, and helpfully this time without calling me a macbot drone apologist…. unlike some wink

    So fair enough, you do have the right to make as big of a deal about the problems, like I already said. But I still do think a lot of those things are small problems, such as the iPod photo wipe thing, or the iPod volume thing, and especially the upgrade thing (seeing as you don’t appear to have personal problems yourself. I think you just said it assuming others have problems.)

    I’ve never actually quite known what you’re talking about when you say, “copy folder”. Do you mean when you drag a folder to a location already containing a folder under the same name where it then says, “There is already a folder in this location with the same name. Do you wish to replace it?” ?

    Because if that’s what you’re talking about, I haven’t actually experienced a problem with that myself. BUT moving from Windows, I would expect it to replace each individual file and keep any ‘other’ files intact within the original folder. But fair enough, Apple do actually use the word, “replace.” But they could easily give the option to do one or the other, like Windows.
    Maybe it’s that way because of applications. Because they are contained in their own folder represented as the .app icon, when upgrading, you would want that overwritten entirely, rather than merged with the old one.

    I assume there are some Apple employees who read this, and hopefully your problems will remind them to do something about this. Or you could send your article to the feedback form. It worked for me: I begged for a Yellow iPod mini for months and look what happened! :D ....they discontinued the product altogether…

    Okay, so don’t think I’ve let you off easily this time, Chris. I’m just in a good mood because it’s my birthday today, so I’m not laying into you as much in this post :D

    Luke Mildenhall-Ward had this to say on Apr 17, 2006 Posts: 299
  • Thanks Luke. It’s the problem with being staff - I have to keep it polite! wink

    You’re right about the “copy folder” problem.

    Or you could send your article to the feedback form. It worked for me: I begged for a Yellow iPod mini for months and look what happened! :D ....they discontinued the product altogether…

    lmao

    There’s an old saying that says “It’s the little things that make the difference.” That is very true of Apple. I noticed it when I switched. They all add up to make a big difference to the user’s experience. So maybe hopefully some of these little things I raised will be dealth with by Apple.

    As far as your birthday goes, well, that’s another one of those little things that adds up. And before you know it you’re a grumpy old bastard like me! smile

    Have a good one.

    Chris Howard had this to say on Apr 17, 2006 Posts: 1209
  • Hehe. Thanks =)

    Luke Mildenhall-Ward had this to say on Apr 17, 2006 Posts: 299
  • Page 3 of 3 pages  <  1 2 3
You need log in, or register, in order to comment