I'm at a local Apple store looking at a 21.5" iMac. After playing around with it for a while my eyes began to feel tired, and while I'm sure it has to do with the screen size (I did lower the brightness to reasonable levels), I don't know if this is a symptom of getting used to working on a 17" laptop for the past 2 years, and is something I can get used to, or is it just that the screen is really too big for long periods of reading. What do you think is the best screen size for programming? Do you program on an iMac? Would you recommend it? I realize this is somewhat subjective, but if I'm about to spend lots of money I'd like to have some stats, even subjective ones.
feedback
|
migrated from stackoverflow.com Feb 7 '10 at 17:40
This question came from our site for professional and enthusiast programmers.
|
For screen size and resolution I always followed the simple rule: bigger is better. I don't think there is something as a too big screen for programming. There is hardly any hardware upgrade you can do that improves productivity more than getting more screen space. Every time I got a bigger screen I found it amazing how much space I had for a while, but by the the time I became accustomed to it and began looking for bigger options again. Since 2 years I'm using two 30" screens with 2560x1600 pixels each but wouldn't mind if they had a higher resolution. | |||
|
feedback
|
|
An ideal screen should be able to fit at least 500 lines of code on it. That way, in code reviews when someone nags you about splitting up a long method, you can say "It fit on my screen.". | |||||||
feedback
|
|
Dual monitors are a huge productivity boost for developers. I have 2 20" 1600 x 1200 monitors at work, and 2 20" 1680 x 1050 monitors at home. I miss them when I'm on my laptop (1920 x 1200). Even dual monitors is sometimes cramped when you need your development environment, database tools, multiple browser windows, and project tracking app all at once. It's almost impossible to have too many pixels as a developer. It's sure possible to have not enough pixels. If you're getting eye-strain on your monitor, there are a number of things to try. Larger font. Different font (I hate Courier!) Higher contrast, or reverse coloring. | |||
feedback
|
|
I use 2-3 24" screens depending whether I'm at home or at work (iMac 24" included) 8) If you're having a problem, try increasing the ambient light level around your workstation (not direct light) to reduce glare, as we get older our eyes need more light to see properly 8) | |||
|
feedback
|
|
I your eyes get tired, try a bigger font. I always prefer bigger screens with high res. Currently I use two 20" with 1600x1200 | |||
|
feedback
|
|
I don't know much about screen sizes, but I prefer using screens with 4:3 aspect ratio for programming, because then I can see more of the code - I tend not to write long lines of code, I split them up. The aspect ratio would also depend of how you develop...if you are using a huge IDE with various panels (one for debuging, one for console output, one for structure, ...) then 16:9/16:10 would be better I guess...I don't use that stuff so 4:3 is great for me... | |||
|
feedback
|
|
a good screen size for programming is the one you are used to. cause that means less distraction. except if you have some serious complains about the old one. no other big rule i guess. | |||
|
feedback
|
|
Bigger and/or more screens is always better. If you're having trouble reading the screen you can always make the editing windows narrower. Your eyes do have trouble tracking across long lines. That lets you put more windows and code on the screen at the same time. I find that to be a big help. | |||
|
feedback
|
|
A good screen must have the following properties (in my opinion):
Furthermore, for not getting tired, choose a syntax coloring that you like. I have a monitor with the aforementioned properties (HP L2245wg) and I never get tired while coding (even though I have glasses). | |||
|
feedback
|
|
i use 1920x1080 on 22". if your eyes get tired use a glasses and eye drop for wetness | |||
|
feedback
|
