Live data from Hacker News

Hack: A typeface designed for source code

sourcefoundry.org

241–249 of 249 posts

Re: Hack: A typeface designed for source code

#241
post #73

I'm slightly surprised that almost nobody here uses Menlo or Monaco, even though several screenshots in the thread are clearly made on OS X. I'm curious why that's the case. Do people generally dislike the system-provided fonts or are the alternatives considered "better"?

I came to Mac OS recently from Linux and while I like Menlo, I found myself quickly going back to Inconsolata[1], which is really great for long coding hours, and works especially well for me with the dark solarized color scheme.

[1]: http://www.levien.com/type/myfonts/inconsolata.html

Re: Hack: A typeface designed for source code

#242

I hate it when sites like this change the normal scrolling behaviour. I use the trackpad on my MBP and on sites like this scrolling accelerates too quickly and gestures like going back don't work in chrome.

This. Why do people think that changing default behaviour is ok? Hijacking scrolling always bothers me, for now I can't even read the content because of the scrolling being too annoying.

Maybe I should write a browser extension to remove scrolling hijacking.

Re: Hack: A typeface designed for source code

#244
post #230
post #221

Earlier quoted context omitted.

Fortunately we can call that a fork, since they comply with the license. https://github.com/chrissimpkins/Hack/blob/master/LICENSE.md

Copyright infringement != plagiarism. They're not violating the copyright because they abide by the terms of the license. They're also not plagiarising because they clearly cite its original source. They even go so far as to say "deeply rooted in" which seems to me like a euphamism for "virtually identical to". The point here isn't that it's illegal or immoral, just kind of uninteresting.

If, for example, someone repackaged a public domain font without attributing source, I wouldn't call that plagiarism either.

In my definition of plagiarism it implies unauthorized use (i.e. not complying with the license) but I guess that's open to interpretation.

So it'd still be uninteresting, unimaginative, not original work... but not plagiarism.

Re: Hack: A typeface designed for source code

#245
post #51

Hack is DejaVu sans mono. Below is a gif I took switching between DejaVu sans mono and Hack. Aside from line height I fail to see the difference. http://gfycat.com/SomberUnitedGermanshepherd

If it's not very different from DejaVu Sans mono, why not use the latter itself in the first place?

Re: Hack: A typeface designed for source code

#246

Earlier quoted context omitted.

ttyp0 is way better than Terminus, which is so popular among Linux/Unix people. But if the world ever goes HiDPI, I guess bit-mapped fonts will die out.

> But if the world ever goes HiDPI, I guess bit-mapped fonts will die out. No, it's the other way around. Anti-aliasing is a hack to make low-res displays slightly more palatable. Once the resolution gets good enough, there's no point in anti-aliasing your fonts anymore, and bitmaps start making a lot more sense.

How is anti-aliasing related? I was thinking about rasters: if you don't have many pixels, you need to use every single one the best possible way, so you manually layout every single pixel. If I have a ton, I can draw any vector glyph and I would not need to micro-manage the pixels. Can you elaborate or give me a link?

Re: Hack: A typeface designed for source code

#247
post #13

I desperately want to find a new code font to love but I always return to Consolas.

Paid, but interesting: Pragmata Pro: http://www.myfonts.com/fonts/fsd/pragmata-pro/ Triplicate T4c: http://practicaltypography.com/triplicate.html Something a little different: Fantasque: https://github.com/belluzj/fantasque-sans

I use Triplicate as my standard fixed size font everywhere. I love it!

Re: Hack: A typeface designed for source code

#248
post #73

I'm slightly surprised that almost nobody here uses Menlo or Monaco, even though several screenshots in the thread are clearly made on OS X. I'm curious why that's the case. Do people generally dislike the system-provided fonts or are the alternatives considered "better"?

I've been using Monaco 9 since I first started hacking away in HyperCard and BBEdit, and when OS X started screwing up the antialiased version of it I switched to ProFont which looks identical but scales properly

Re: Hack: A typeface designed for source code

#249

Earlier quoted context omitted.

> But if the world ever goes HiDPI, I guess bit-mapped fonts will die out. No, it's the other way around. Anti-aliasing is a hack to make low-res displays slightly more palatable. Once the resolution gets good enough, there's no point in anti-aliasing your fonts anymore, and bitmaps start making a lot more sense.

How is anti-aliasing related? I was thinking about rasters: if you don't have many pixels, you need to use every single one the best possible way, so you manually layout every single pixel. If I have a ton, I can draw any vector glyph and I would not need to micro-manage the pixels. Can you elaborate or give me a link?

It takes far less cpu time to draw a bitmap than to draw a vector shape. An in-between solution is to pre-render vector shapes into bitmaps for later use; this is what METAFONT does.
Post reply on HN