News for hackers. Stuff that matters.
Re:Google's updated Java coding guidelines by judk on Wednesday January 29, 2014 @10:36PM (#7148931)
What are you doing that ASCII art is a major factor in code readability?
Re:Google's updated Java coding guidelines by vinkelhake on Wednesday January 29, 2014 @11:52PM (#7149132)
Never said it was.

I spend a lot of time reading code. I read other peoples code every day. To a very large extent, that code is going to use various layout tricks that are based on a monospaced font. Someone might line comments up like this:

    // 1. Blah blah, blah
    //    blah and more blah.
    // 2. Second piece of blah.
Arguments to a function might be lined up:

    void func(int arg1,
              int arg2...
Someone might describe some detail of a network protocol with a diagram (as often seen in RFCs). A large comment block might be adjusted to fill out to a certain column width. I'm probably forgetting a ton of other layout tricks that people use. Almost all of them rely on a monospace font.

Looking at code that wasn't specifically written for proportional fonts is death by a thousand cuts. The readability suffers greatly.

Re:Google's updated Java coding guidelines by userbinator on Thursday January 30, 2014 @05:08AM (#7149862)
This reminds me of some people who try to do ASCII art in a proportional font in a plaintext email, which then looks completely munged on everyone who uses monospace fonts or a different proportional font. IMHO plain text files should always be read/written in a monospace font, as otherwise you limit the expression of the medium unnecessarily since ASCII art becomes no longer "portable".