HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
jgm
pandoc
Haskell2012–2026
jgm / pandoc

pandoc

Universal markup converter

56Distinct people
63Mentions
1Explicit recommenders
46.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Universal markup converter

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I really hope that they borrow a lot if not everything from pandoc[1]. My only real complaint with pandoc is the table formatting, but I think fiddlosopher is adding org-mode…

dfc used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 AM UTC.

A technical vision for the Haskell ecosystem direct repository linkDebated

Commenters debate whether Haskell's primary bottleneck is technical performance, such as compile time and incremental builds, or its lack of a coherent, polished ecosystem for building diverse applications like web and desktop software. While some argue that foundational libraries and better developer experience are the missing pieces, others contend that the language's utility is constrained by fragmented tooling and unclear positioning compared to more universal alternatives.

17 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4

Mentions over time

HN mentions by year63 dated mentions

Observed mentions: 2012-02-25 18:15:18 UTC to 2026-10-01 15:56:48 UTC.

02468102012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC404
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC000
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC303
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC505
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC202
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC514
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC303
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC303
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC312
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC817
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC404
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC1019
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC211
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC404
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC716

What Hacker News says

4 sources
For programmers today, an option to consider is to use plain TeX directly, by writing in Markdown or whatever, and generating the `.tex` file via a preprocessor program. After all, the facilities that LaTeX was written to provide (automatic section numbering, references, etc) can just as well (or even, more sanely) be done outside the TeX engine. There is a catch or two: • Writing the preprocessor will still be a bit of work — I think a promising approach is to use Pandoc, but no one has yet merged a plain TeX writer into the Pandoc repo (https://github.com/jgm/pandoc/issues/4341 — I was briefly interested a couple of years ago, and may look into it again: it doesn't seem like a lot of work honestly). • The main reason people use LaTeX is because of all the packages in its ecosystem that do various tweaks to the typesetting. (This is also
Read the rest
the main problem with LaTeX: TeX itself is good; LaTeX itself is mostly fine; it's the menagerie of packages of varying quality and conflicting effects that cause all the problems that LaTeX users usually complain about.) And in the LaTeX ecosystem, there does not exist a culture of teaching how to do things without the package (just as "You might not need jQuery" is not written by the jQuery authors), so if some LaTeX package looks attractive to you, you're back to LaTeX package hell. I have some ideas here of making it easier to "steal" from a LaTeX package by showing the equivalent "generated" TeX, but they require a bit of work hacking on the TeX engine, and have never got around to it. Anyway, in the meantime, writing in Markdown and using Pandoc to generate a LaTeX file remains a good approach IMO.
In LaTeX Makes Me Angry
A few more: https://github.com/simonmichael/quickbench - Easily time one or more commands with one or more executables and show tabular results https://github.com/simonmichael/shelltestrunner - Easy, repeatable testing of CLI programs/commands https://github.com/simonmichael/hledger - Robust, fast, intuitive plain text accounting tool with CLI, TUI and web interfaces https://github.com/haskell-game/fungen - A lightweight, cross-platform, OpenGL-based 2D game engine in Haskell https://haskell-game.dev - a small selection of the many games written in Haskell https://haskell-via-sokoban.nomeata.de - Haskell via Sokoban https://lhbg-book.link - Learn Haskell by building a blog generator https://github.com/input-output-hk - the Cardano blockchain and Daedalus wallet https://github.com/jgm/pandoc - Universal markup converter (already mentioned
Read the rest
above) https://github.com/simplex-chat/simplex-chat - secure messaging platform https://www.libhunt.com/l/haskell - more projects...
In Dhall: A Gateway Drug to Haskell

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.