I almost complained about having non-monospaced fonts as a default on the linked page for 'coding', until I started reading this page where they explain the reasons. Still, mono-spaced is much easier for an IDE to interpret and my brain thinks me like it more.
I even did an HN search, but I didn't think to look for "fonts" instead of "font".
Strangely, it seems the HN search will exact match on the initial search and then prefix match after that. Compare URLs:
Initial search
https://hn.algolia.com/?q=input%20font#!/story/forever/0/input%20font
Add an 's' then remove it
https://hn.algolia.com/?q=input%20font#!/story/forever/prefix/0/input%20font
Same search term shows in the box, but the results are different.
We're working on a more sophisticated dupe detector that will do this kind of matching automatically, so hopefully the days of tracking all this down manually (for both our sakes!) are numbered.
Proportionally spaced fonts are nice on the eyes. I've been using Input for the last few days and it makes code much more pleasurable to read... Mostly.
But I found that I rely on intra line alignment often and proportional fonts cannot deliver that. The end result is so ugly as to completely overwhelm the advantages.
Elastic Tabstops[1] are the solution, but support is too patchy, and getting a team to agree on tabs vs spaces for line indents is hard enough, without then getting them to all follow elastic tab practices for laying out aligned content.
Yeah it looked ok to me. Looks like it was designed for python. On my clojure files the parens/brackets get lost. Granted editors mostly make parens easy but i still have to be able to scan for them.
