@kirby Don't get me wrong, it's not because I think all bitmap fonts re ugly — actually that is what I kept using til probably early 2010s, when antialiasing stopped being a performance hit and became near-zero effort for the hardware. So no, not all bitmap fonts are ugly — it's just this one, especially at this size. It looks inconsistent with characters using different stroke widths, take lowercase letter "e" for example — it's lower "tail" part is lighter than the rest of it, and it puts an extra strain on the eye. I don't mean that it's completely unintelligible — but if I'd be spending extended periods of time staring at text, I'd like to avoid such things. And it's like Pike took a particular liking to ugly fonts. Go fonts are another perfect example of this: https://go.dev/blog/go-fonts I really want to like them, but I just can't… Look at them, they are fucking ugly! :marseyeyemixer3:
@kirby@m0xEE I mostly use sam with p9p just to have fixed width spacing, and if I have p9p available to me I probably also have drawterm, so I'd probably just use acme over drawterm anyway
@sysrq Precisely! I know that having personal preferences isn't out of the question, there are professionally-done commercial fonts that I absolutely despise, but this isn't the case, I do my best to remain as objective here as I possibly can. Having different-width strokes is okay for decorative fonts, but not for general purpose ones. Then again, there are tiny details that are helpful as they help tell the characters apart seamlessly and there are those that only distract you — the latter shouldn't be the case for font that you stare at all day, that's it. @kirby@sysrq
@kirby Damn, I didn't paste the link 🤦 Here: https://github.com/fcambus/spleen It's monospace font though, but it's a bitmap one, and there are examples there of how it looks in different resolutions, see for yourself how it fares, even with 5x8 characters it's still nice.