Originally posted by: Leyawiin
Originally posted by: VirtualLarry
Originally posted by: Idontcare
The very concept of a "dead-pixel policy" just grinds my gears to use a Peter Griffin phrase.
Imagine if you bought a 1GB dimm and but only 0.98GB actually worked, there were some bits that were just dead. Oh well, that's your problem.
Or what if you bought a CPU and everything worked except one of the SSE4 instructions. Every time your app tried that application it generated an error.
The difference there is that those are functional errors. A bad pixel is just a cosmetic error, the display doesn't need all the pixels to function properly.
A quality panel shouldn't have any and a bad placed group of two or three stuck pixels in the middle of the screen can ruin your viewing experience. Dead/stuck pixels are defects and the industry, in an effort to lower prices and gain market and resigned itself that a certain number of LCDs going out the factory door are defective in that regard. The cost of replacing them is factored into doing business and they have no intention of "quality control" canning bad screens.
It may be "cosmetic", but I wouldn't accept a new car with a big scratch on the side, rip in the upholstery or crack in the middle of the windshield, never mind it still goes down the road.
I agree with your sentiment but I disagree that a stuck pixel is cosmetic and not a functional issue.
The purpose of an LCD is to make the pixels display colors as requested by the video card. A dead pixel is a non-functioning pixel. Very analogous to dram.
Now you may choose to disregard the non-functioning pixel and keep using the display. You can choose to disregard many memtest+ errors and your rig can in some cases keep on functioning with no stability issues.
A cosmetic defect on an LCD would be something like a scratch in the plastic housing the LCD, or discoloration in the stand, etc. But the function of a LCD is to display colors thru its pixels, something it doesn't do with dead or stuck pixels.
For your car analogy this is more like a flat tire, sure you can drive the car on a flat tire but its not performing to your expectations as that point.
Making the argument that the ramifications of a non-functioning pixel is merely a reduced subjective experience doesn't make it any less of a functional/non-functional argument. I could argue that system stability is a subjective thing too, and as such instability brought on by non-functioning bits is merely a subjective problem for the user. But I suspect such an argument would be shot down (for all the right reasons).