GitHub is releasing two open-source fonts: Mona and Hubot Sans
github.com
github.com
Someone's gonna lose a LOT of crypto over this.
Ill Ill Ill Ill Ill
in Mona Sans:https://i.ibb.co/3mv1Myx/Ill.png
What a pleasing symmetry.
> Licensed under OFL (basically, use it on your site or in your app and credit GitHub—read the full license)
Requiring only attribution and nothing else is very generous and only fair. Would be a serious dick move if someone fails to do even this, more so if it's for a commercial product.Where can we find a similar such thing for the sources repurposed and/or redistributed for or through Copilot, anyway?
Examples:
I revisited that page after reading HN comments and then noticed that mouse pointer is actually changing weight and width... doh.
Is this common for F/OSS fonts? I don’t know that I’ve seen many fonts that require attribution.
TIL any the OFL (https://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id...)
If so, the answer is that fonts are a major underpinning of how an organization or a product is presented to the world.
To make an analogy that the hn crowd might understand, the value of a typeface for a design system is like the value a cryptographic primitive or a library like openssl to a functioning security system.
Nobody (aside from designers and typographers) will think "oh wow that font is so great they must have invested a lot into it", but it underlies every written visual interaction between the brand/product/company and its audience.
That said, are there many other fonts available that fall into the appropriate style, usage, licensing terms, etc that GitHub need? Perhaps. But uniqueness is a value in itself, and having a decision about a set of fonts that the company uses is a pretty important thing.
It's like the 3 spaces or 4 spaces vs tabs discussion. Some people use one, other people use another. But in a company, having an approved typeface that is recognized internally as the typeface to use (of course, you can have different typefaces for different scenarios/uses) - is just as important as determining which one to use.
Maybe if they spent less resources on achievements, fonts, etc. and more on reliability they could improve their downtime, which seems to be happening more and more often.
This is where the wide parameterization of the fonts comes into play: "use one of those two fonts, feel free to go wild with the parameters" is much more likely to actually be followed than "use one of those n fonts, no exceptions", for almost any value of n. And better for morale as well.
/s
Realistically, this is probably very cost efficient as it’s a relatively low effort project compared to a fully fledged feature, and something that can make someone say “hey, that y reminds me of GitHub”.
See also IBM Plex: https://www.ibm.com/plex/