Comic Sans is the ultimate coding font.

Discuss.

>>40
Nobody said anything about real-estate. Regardless, why would you ever need to see more text than that at once?

What's the deal with these really fucking small fonts? My fonts are about the same size as >>33's, maybe even a bit bigger. My vision's not all that bad and I could use much smaller fonts, but decently sized fonts are much easier on the eyes.

You really don't need to see shitloads of code at once; if your functions are longer than the ~40-50 lines you get with a decent font on an average monitor, you have bigger problems than just font size.

>>42 you have bigger problems than just font size.
Screen resolution?

>>43
Lack of abstraction.

>>42
It's not about big functions, it's about having documentation, multiple source files, project shit, etc etc etc, all visible at once.

>>33
Blurry fonts are blurry.

>>45
Multiple screens + tiling window manager.

>>46
I never understood this argument. Do you have like perfect vision or something?

>>48
I can see RGB subpixels & phosphors at normal viewing distance.  Reading newsprint and magazines is annoying because I can see the color dithering.  I can read microprint on checks and credit cards, but only if I put it really close to my face.

>>49
You sound like you're saying you're special, or an exception.

>>48
For looking at a computer screen, being nearsighted is just as good as having perfect vision.
Even if you were farsighted, a pair of glasses should enable you to easily see the difference in clarity between a bitmap font and an antialiased one on just about any LCD monitor, except maybe those high-resolution low-area laptop screens.
The importance of this diminishes with larger font size, of course.

>>48
I never understood this argument. Do you have like a badly focused CRT or something?

>>34
Looks like DejaVu(/Bitstream Vera) Sans Mono.

NSimSun is the best coding font. It's very beautiful.

>>54
Is it Touring Complete?

>>50
I fully expect people who have been poking pixels for 20 years to have the visual training of seeing such detail.  It's >>48 who is the exception, thinking that it's something special to notice pixel-level detail or blurring.  It is not, therefore it must be clear, and preferably small because wasting GUI space is just plain stupid.

/prog/, this thread is starting to look like your average /g/ discussion. Don't do it again.

>>57
I am not entirely sure that that wouldn't be an improvement.

>>45
What for? Unless you have the eyes of a chameleon, you can only look at one of those at a time anyway.

>>59
Your average /prog/rammer has eyes like a chameleon, or at least some kind of reptile.

>>60
Some kind of reptile...? Like... a /prog/snake?

>>60
I was referring chiefly to the chameleon's ability to focus its eyes independently. If most of /prog/ can do that, I want you to teach me now.

>>62
You have to meditate and focus on SICP. The rest comes naturally

>>62
Moving eyeballs and focusing on something else then back is a fuckload faster than clicking/keypressing to scroll somewhere and back.

>>64
Meaning you never have to remember anything, and you waste how much time looking back and forth?

>>65
Your argument is valid for small shitprograms only.

>>66
You're so reliant on CONSTANT REFERENCE ALL THE TIME that you can't even follow my argument. The argument is:

1. The amount of time it takes to switch views varies in significance depending on how often you do it. Below a certain point, it is completely insignificant.

2. In order to switch views less often, it is necessary to remember whatever you just read.

3. If you put everything on the screen at once, you need to switch views, and don't need to worry about the overhead.

4. There is, however, time lost every time you look back and forth, but it's easy to miss because you're thinking about what you're doing (finding the right spot to refer to, looking back, remembering where you were).

5. Since it's so easy to do this and so easy to miss the downside, you will do it all the damn time, disorganizing your thoughts and slowing yourself down.

6. It's better to develop the ability to remember what you just fucking looked at. Read, read, write, write is much more efficient than Rweriadte,r , wreiadte.

>>67
3, should of course be "don't need to switch views".

>>67
Your argument is valid only for people with brain damage affecting their memory.

>>69
Untrue.

>>70
False.

ZOMG OPTIMISED

>>71
Don't you "zoh my goptimize" me.

>>72
huh

>>71
nil

>>74
{}

>>75

Looking to find fault where there is   a wealth of   information on the   couch I always   ping random addresses   i come across   it feels like   it takes too   long But if   I try to   optimize just the   same as functions   And with this   for very long   time Im running   windows so no   one knows GTK2.

Wreiadte.