Ask HN: Your code editor, black on white or white on black? • Hacker News Board

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

#101

Post by tincholio » Tue, Dec 20, 2011, 4:15 PM UTC

wollw wrote: post #31

hellweaver666 wrote: post #8

I tend to use a light to medium grey on black because I don't like the mega contrast of white on black. But for the purpose of your survey, I answered 'white on black'.

Likewise. Also, I don't like highly saturated colors. I've tried a few different color schemes and while I did like Solarized Dark I keep coming back to Zenburn[1] for its muted, low contrast palette. I haven't found anything better. [1] http://slinky.imukuppi.org/zenburnpage/

+1 Zenburn is awesome for long sessions in fron of the editor.

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

#102

Post by swah » Tue, Dec 20, 2011, 4:17 PM UTC

nvk wrote: post #89

I like preserving my sight as much as possible, so dark (not black) with light (not white) pastel colors.

Which one on the background?

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

#103

Post by krupan » Tue, Dec 20, 2011, 4:20 PM UTC

emacs: color-theme-dark-blue2

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

#104

Post by rcfox » Tue, Dec 20, 2011, 4:25 PM UTC

w0utert wrote: post #62

idan wrote: 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 sh…

> Text gets blurrier quicker than when using a lighter background.

Perhaps you need to get glasses. I've never had text go blurry on me, regardless of the colour theme or duration.

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

#105

Post by bilban » Tue, Dec 20, 2011, 4:35 PM UTC

mhd wrote: post #92

Depends a lot on the general setup. On my Mac, it's often a white(-ish) background, whereas on a shell-heavy Linux desktop I keep with a general dark look and feel. But lately I surprisingly often turn to yellow on blue (TP-like), without syntax highlighting…

I switch to light on dark depending on ambient conditions, my study is really gloomy and I work at night, so a bright screen blinds me.

On OSX10.4 at least I use the accessibility switch for this - sadly the anti aliasing looks worse with a dark background.

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

#106

Post by bilban » Tue, Dec 20, 2011, 4:38 PM UTC

rcfox wrote: post #104

w0utert wrote: post #62

Earlier quoted context omitted.

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 sh…

> Text gets blurrier quicker than when using a lighter background. Perhaps you need to get glasses. I've never had text go blurry on me, regardless of the colour theme or duration.

I can't read a white background unless I'm in a very bright room. Off whites are better for me. But personally I prefer light on dark. But it's a personal thing.

I rue the day the browser default background colour changed from being light grey to white.

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

#107

Post by andys627 » Tue, Dec 20, 2011, 4:39 PM UTC

I remember eading th ebest was white that matches ambient light (i.e. if its dark in the room, turn the light on)

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

#108

Post by bilban » Tue, Dec 20, 2011, 4:40 PM UTC

I think you should just leave it down to your desktop defaults, that should ideally be configurable in one place.

It's annoying going through each app setting them up individually.

Each to their own.

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

#109

Post by miles_matthias » Tue, Dec 20, 2011, 4:50 PM UTC

White and other bright colors on black.

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

#110

Post by chimeracoder » Tue, Dec 20, 2011, 4:55 PM UTC

w0utert wrote: post #62

idan wrote: 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 sh…

> In my experience dark backgrounds with light text are more tiring on the eyes in long coding sessions.

I completely disagree; my eyes tire looking at a light screen much more quickly. Sometimes I'll invert the colors late at night just to make things easier to read.

(Come to think of it, thanks for reminding me that I need to figure out how to get xcalib working with my external monitor, not just the laptop screen...)