Live data from Hacker News

Ask HN: Your code editor, black on white or white on black?

docs.google.com

61–70 of 127 posts

Re: Ask HN: Your code editor, black on white or white on black?

#61
post #53

Earlier quoted context omitted.

I use wombat too, its easy on the eyes and a very aesthetically pleasing color scheme.

Customized Wombat, yep.

Customized murphy.. ( contrast junkie! http://i.imgur.com/CEY5P.png )

Re: Ask HN: Your code editor, black on white or white on black?

#62
post #59

There's a solid usability reason why inverse (light-on-dark) is better for anything with syntax highlighting, like terminals and code. Many colors of the spectra have poor contrast with white when used in an emmisive light context, like your screen. Yellow on white is illegible because it lacks contrast. The range of distinguishable, saturated colors is much larger on a black background, and you can comfortably add a…

I agree about the point you make about contrast and syntax hihglighting, but I disagree with your conclusion.

In my experience dark backgrounds with light text are more tiring on the eyes in long coding sessions. Text gets blurrier quicker than when using a lighter background. I came to this conclusion after years of using dark backgrounds, and having switched to light backgrounds.

Personally, I think the question should not be 'white background or black background', because IMO a light gray or blue background is even better. Borland was on to something with their C++ and Pascal IDE's ;-)

Re: Ask HN: Your code editor, black on white or white on black?

#65
At work my stuff is mostly done through puTTY, I set up different profiles for our Dev, QA, and Prod equipment that use green/yellow/red themes respectively.

At home its default Eclipse theme (light) but that's mostly because of pure laziness. This thread has been a good reminder to change that after my reformat this holiday :)

Post reply on HN