How Would You Write A Computer Lemon Law?

from the not-so-easy dept

Ed Foster has written up a short blurb for Gripeline discussing how complicated it would be to write a "lemon law" for computers, but suggesting that one is still needed. As he notes, it's not as easy as just replacing the word "automobile" with "computer" in existing car lemon laws. After all, there are many different reasons why a computer would stop working -- and not all of it has to do with the hardware. However, putting a software exception in place would then just make computer manufacturers more likely to quickly blame software problems for any issues. Of course, a few years back some were suggesting that we needed lemon laws for software as well, so maybe the answer is to write an inclusive lemon law. To be honest, however, it's not entirely clear that such laws really are necessary. While my own personal experience suggests that many computer makers are quite resistant to admitting they sold you a lemon (my laptop with 6 failed hard drives in 18 months was a fun one to deal with), there are enough services and outlets for people to now make their problems very, very public -- and that's made some computer makers much more responsive. So, perhaps it's as problem that works itself out, as computer makers recognize that there is a huge cost in public relations damage to not responding to complaints.

Reader Comments

Subscribe: RSS

View by: Time | Thread


  1. identicon
    Casper, 25 May 2007 @ 8:49am

    Re: I wouldn't

    I don't know, they may have good reason for suing MS in some cases. A lot of the computers we order have to be wiped and reinstalled from the ground up to get everything working and detecting like it should. In fact, one of my laptops (I won't mention the brand) came brand new with the drivers all wrong from the manufacturer. My processor was detecting at less then 1/3 speed it should and my through put was nil. I had to manually reload all the drivers twice to get XP to use it correctly and no one could decide who was to blame.

    How do you assign blame? Is it the fault of the people who wrote the software, the people who installed it, the people who wrote the drivers, or the people who made the hardware?

Add Your Comment

Have a Techdirt Account? Sign in now. Want one? Register here



Subscribe to the Techdirt Daily newsletter




Comment Options:

  • Use markdown for basic formatting. (HTML is not supported.)
  • Remember name/email/url (set a cookie)

Follow Techdirt
Techdirt Gear
Show Now: Takedown
Advertisement
Report this ad  |  Hide Techdirt ads
Essential Reading
Techdirt Deals
Report this ad  |  Hide Techdirt ads
Techdirt Insider Chat
Advertisement
Report this ad  |  Hide Techdirt ads
Recent Stories
Advertisement
Report this ad  |  Hide Techdirt ads

Close

Email This

This feature is only available to registered users. Register or sign in to use it.