🚀 go-pugleaf

> You have the word "proportional" backwards - you
> are using it to mean "monospaced", while in fact
> it means just the opposite.

Indeed I have switched the two. Want I meant to say is I advocate
viewing code in non-proportional (or monospaced) fonts.

> Italics are used for comments here - and they are green - not red.
> Red is reserved for highlighting errors.

Yes, seeing the code in different colors for diffentent things is
beneficial. But this is added by the editor/IDE, not the developer.
The only thing actually stored with the code is the CODE. That is, not
other semantic information (font, color, etc) is stored along with it.
The entire meaning of the code is represented by the characters in the
code, period. All other affects that may clarify the meaning of the
code are applied by outside tools, as it should be.

This entire point was brought up my somebody who (I believe) claimed
that non-proportional fonts were as antiquated as mechincal
typewriters and served no purpose. I completely disagree. I don't see
how you can view code so that it is aligned clearly in anything but a
non-proportional font. Am I mistaken? I am not claiming the all
documents should be written in something like Courier. I do think that
monospaced fonts serve a clear purpose in code.

Also, the other part of this whole topic was the tabs vs. spaces
thing. It has been stated repeatedly that spaces are represented
consistently across all tools - they represent ONE SPACE. Tabs,
however, are interpreted differently. Some tools show eight spaces.
Some four. Some show a box. Some show some other weird character. Yada
yada yada. What it all boils down to is this - if tabs are not
represented consistently universally, why use them over spaces? I have
yet to hear a reasonable answer.

Ryan