I really like the curly braces in Input. I'm not too thrilled about the licence though. And I've used DejaVu Sans Mono for too long for anything else to look right to me, I think, and the DejaVu fonts have such great glyph coverage as well.
Input: Fonts for Code
91–100 of 136 posts
Re: Input: Fonts for Code
#92I'm a font-aholic and reading Hacker News, I get the impression I'm not the only one. My first adventure down the font hole started with Bit Stream Vera Sans Mono followed by Source Code Pro. Stuck with Source Code Pro for many years and even today, not sure any other aliased font looks and works as well as Source Code Pro at almost every size, from the smallest onward. It just looks clean to me. After reading on her…
> Operator Mono
That's one funky monospace, with almost Flintstones' feel to it.
Re: Input: Fonts for Code
#93Recently found the Golang fonts. https://blog.golang.org/go-fonts Monospaced with serifs - totally blew my mind. I am using it since then and it is the best font for me I have tried so far.
Yeah, ever since they released those I've been using Go Mono in my terminal (and thus in Vim for coding). I'm not even particularly particular about fonts—I do care a little though—but this one just sat really well with me.
Re: Input: Fonts for Code
#94I'm a font-aholic as well, but I specifically look for fonts that remind me of the early days of computing. I really like IBM Plex Plex Mono and Golang's monospaced serif font. I also found vt52 from back in the PDP days.
Another interesting font is B612 Mono, which is the font used on aircraft to help pilots easily distinguish characters on their HUDs. I used it as a programming font, and I think it's quite legible.
Re: Input: Fonts for Code
#95I've been using Input for years. Specifically, I've been using Input Sans Compressed. Yes, it's a proportional font. I've gotten so used to it that monospaced fonts feel like there's just way too much whitespace.
Re: Input: Fonts for Code
#96To be honest, I never understood all these discussion about "coding fonts". They pop up every now and then here on HN but it always seems like bikeshedding to me. Don't get me wrong - I'm aware that there are some folks who may have a vision impairment or some other reason where it really matters. But apart from that, I've been programming for decaded on many different computer systems with many different fonts, and…
Way too many stock monospace fonts make it hard to distinguish between lowercase ell, capital eye, numeral one, and pipe. All of those except pipe should have different serifs. (I feel like this is a problem even in proportional fonts, incidentally. I like sans-serif as much as the next guy, but if the word "Ill" looks like chicken-scratches then something is wrong.)
And yet, as I mentioned in my original post, I've been coding and using the shell etc. for decades and never ran into that problem in practice.
I would bet that more production time has been wasted on a global scale with discussions about and fiddling with font options than with a wrong l, I, 1, | in a place where it shouldn't be.
Re: Input: Fonts for Code
#97For fixed-width serif font, I like bloomberg terminal serif font. It's the same family as Georgia but fixed spaced.
https://qph.fs.quoracdn.net/main-qimg-ecd90601a357e090eadf2d...
Re: Input: Fonts for Code
#98I like lower case parentheses, for Scheme and Lisp coding. The ligatures in Hasklig gave me this idea.
I'm currently using Courier Prime Code with 60% parentheses, vertically centered around the lower case "o", and moved a bit left and right to open up expressions, and for better spacing trailing )))'s after a letter. This is easily accomplished using the demo version of Glyphs Mini, and it puts focus back on the text, without interfering with tools that expect parentheses. (I used a preprocessor for years that inferred most parentheses. It can be done, but then standard editor tools for Lisp don't work.)
There are deep reasons one might prefer Scheme to Common Lisp, particularly as a mathematician. Not liking Common Lisp's default "GET OFF MY GRASS" upper case is a shallow reason. Call me shallow. It was a revelation to realize that I didn't like Lisp parentheses because they were also upper case, and they should also be lower case.
Re: Input: Fonts for Code
#99I'm a font-aholic and reading Hacker News, I get the impression I'm not the only one. My first adventure down the font hole started with Bit Stream Vera Sans Mono followed by Source Code Pro. Stuck with Source Code Pro for many years and even today, not sure any other aliased font looks and works as well as Source Code Pro at almost every size, from the smallest onward. It just looks clean to me. After reading on her…
> Operator Mono That's one funky monospace, with almost Flintstones' feel to it. https://www.typography.com/fonts/operator/styles/
You may also enjoy Fantastique Sans, formerly known as Cosmic Sans, as it is sort of programming version of Comic Sans:
Re: Input: Fonts for Code
#100Used them for a couple years already. Input Mono Condensed!
If the Input Mono Condensed you're referring to comes from https://djr.com/input/ I recommend reviewing that font's license.
https://djr.com/license/ is a non-free license (the license does not respect your software freedoms to run, copy, share, and modify the software). The license is revocable under unclear and incompletely specified conditions: This license can be terminated at any time for no declared reason "without the obligation of notice or opportunity to cure [a breach of any term of this agreement]". The license tries to place limits that could go beyond what power copyright law grants in Massachusetts, USA (the region the license will be interpreted within). In other words, copyright law in your region may grant you more rights than the state of Massachusetts, USA grants.