days are loud, disturbed, and busy in a typical office... nights can be focused, intense, and far more productive when it comes to writing code. (<tangent> I love staring at code so long while malnourished and sleep deprived that I sense vertigo before my monitor =) </tan>) Also, working nights means that one can likely be immersed in electronica or classical or whatever you prefer without sweaty headphones on and there are no neighbors or family members to awake (since most offices are in commercial districts nicely removed from the residential burbclaves) ... so maybe I'm an immature lamer script kiddie whose security blanket is my resemblance of every typical hacker (although not quite as perv as Mouse in Matrix) ... maybe I'm not all or any of those things but I do think this issue is intimately fundamental to every interaction with a computing device. How will we tell it what we want it to do? How will we know that it did it? My main point is that screens don't have to destroy or offend onlooker's eyes... maybe it's like hard plastic seats at McDon's or BurgerChum where they don't want you to get too comfortable so you won't want to lounge about and clutter the dining room so others can buy and dine ... I don't know about you but when the whole thing is actually glaring, radiating, electron beams a beaming and cathode rays arraying) I'd rather focus on a little bright text than gape at fluorescence while trying to dial pupils into a little dark text. Thanks for reading my long winded %re of why I think what I think (and for enduring my poor paragraphing ability). I welcome any further discussion regarding this issue since I feel so passionately about it. I'll try to be open minded but I don't like it when dust gets in there (maybe I need a Microsoft optical intellibrain with lasereye technology). TTFN & Shalom.

-PipTigger