Well I bought one dsl black for me this weekend and it seems to be perfect, no dead or stuck pixels, no cracked hinge, no yellowish screen, not even a button problem, the only thing that is strange is that when i turn off the screen, there seems to be some pixels still lit... but that's no big deal, when I turn on the ds again they r all gone!
The thing about the wires running down the R button. Some ppl say that is why the R button is looser feeling that the Left, but I exchanged my DS lite for another one and now, it is the opposite! The L button is much looser than the R...so i'm just confused now.
you can exchange it as often as you want, there will always be a problem with the ds lite.
either its the l/r buttons, its the d-pad diagonals not working as they should, its dead/stuck pixels, its a yellowish (touch-)screen, a shifting touchscreen or whatever.
unfort. you have to live with it.
though what the poster at http://harmful.cat-v.org/software/java said is true about Java, it isn't so much about C++, C# while preferring C over it. I doubt he'd write a network stack in linux, port a SQL server in C and a mail client if it was a senior C/C++ paid job. You don't even need to care about pointers in C++ if you don't use them and instead use the OOP classes, such as an object reference, which is safer because it guarantees object heritage (Inheritance) which eliminates the need of a garbage collector. Typical use case of this is to use push/pop operators over a vector array, where you don't even need malloc. (it's used internally, yes, but by going the inheritance way you let the C++ to handle it for you)