Thanks, but no. Your foo.bar() example is significantly less readable the way Black formats it.
what, how? Wouldn't the number of spaces you'd need to prefix lines 2 and 3 with vary between fonts?
foo.bar(one
two,
three) //this is fine, and slight drift on different fonts is also fine
My argument is that both fonts are just as good in this situation, and monospaced fonts aren't benefiting here. You don't need monospaced fonts to use formatting 1, you can just choose formatting 1 and then use either kind of font.
Doesn't that mean I disagree with your post?
It's important to note that I'm not comparing monospace versus proportional. I'm saying that "formatting 1 with proportional font" isn't really worse than "formatting 2 with proportional font". Both of them are going to have problems from someone that really likes monospacing.
"If you already decided to have a proportional font, you don't need to stop doing any things."
My argument is that "need to stop doing X" is not true for either kind of font.
One question people sometimes ask is, "How can you code in a proportional font? How do you line things up in columns?"
The answer is you don't. For example, the Black code formatter for Python completely eschews column alignment of this sort:
(Imagine that the words were long enough that the whole thing wouldn't fit on one line.)Instead, Black formats it like this:
No column alignment, only indentation. Code formatted like this is equally readable in a proportional or monospaced font. You don't need monospaced fonts!I've read and written all my code in proportional fonts for close to 20 years. My current one is Trebuchet++, a variant of Trebuchet MS that I customized in FontForge.
Trebuchet MS is pretty good on its own. For example, all of the "confusable" glyphs are easy to distinguish. And it renders very nicely on a high-DPI display.
Its tilde is pretty bad, though. It's tiny and almost looks like a hyphen. So that was the first thing I fixed, putting in a better tilde.
Then I experimented with spacing for the _ and . glyphs. I added negative margin on both sides of the _, while keeping its width. And I added positive spacing on both sides of the . glyph. Consider code like this:
snake_case_name.another_snaky_name()
These spacing changes have the affect of pulling the individual words in each name closer together, while increasing the separation between the two names.
It is subtle, but to my eye it helps readability.
Next up will be to add some positive margin inside the three pairs of brackety things: (), [], {}. I have always found that it helps readability to add a space inside parens and such, but most contemporary code formatters prohibit this. With a proportional font I can tweak the font to put some visual spacing there.