Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderLigatures, IMO, make for a bad coding editor experience. No, I do not want >> parsed as a right shift when it's actually used as two adjacent template delimiters. And no, I'm not okay with the inconsistency that results from the usage of different operators from one programming language to another. Want to change a != to a == operator? Enjoy futzing with placing the cursor properly. It's a cute idea, but I found it more annoying to use in…
As a developer, I have spent years writing and learning to parse the meaning of sequences like ==, ===, <=, ~=, and so on. For nearly all of us, the ligatures in this font are completely new. I think it's a creative and interesting idea, but it means re-training my brain to recognize them, which would take time. And even if I could get my preferred editors to work with it, I would see the traditional symbols when reading code…
Some of the “glyphs” (is that the correct term?), like the arrows (->, =>) look nice but some of the other ones (!=, !==) look too similar and would require a double take to be perceived correctly. It’s an interesting idea and I like the use of the “hidden” features of the True/Open Type System, but I think some of the symbols need a bit more help. Very cool though!
I would disagree that the eye spends any extra time "joining" multi-character sequences. I think it's a matter of what you're used to looking at. I find many of these ligatures harder to recognize than the familiar ascii representations.
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 378
- Total comments
- 237
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2015-05-22 | FiraCode: Monospaced font with programming ligatures | clippit | 11 | 3 |
| 2015-08-17 | Monospaced font with programming ligatures | DaGardner | 3 | 2 |
| 2015-12-19 | Fira Code: monospaced font with programming ligaturesFirst breakout | vdaniuk | 97 | 81 |
| 2017-03-20 | FiraCode: Monospaced font with programming ligatures | tekromancr | 2 | 0 |
| 2017-04-27 | FiraCode: monospaced font with programming ligatures | callumlocke | 4 | 0 |
| 2017-06-25 | Fira Code: monospaced font with programming ligatures | grimgrin | 3 | 0 |
| 2017-10-28 | Fira Code: Monospaced Font with Programming Ligatures | jibcage | 4 | 0 |
| 2018-06-02 | Monospaced font with programming ligatures | dewmal | 3 | 0 |
| 2020-08-18 | FiraCode: Free monospaced font with programming ligatures | natcombs | 1 | 0 |
| 2023-07-19 | FiraCode: Free monospaced font with programming ligaturesHall induction · Best thread · Latest 20+ point return | Lwrless | 247 | 150 |
| 2025-11-11 | FiraCode: Free monospaced font with programming ligatures | tyleo | 3 | 1 |
