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 orderI've argued that parinfer complicates lisp editing. Some notes critiquing parinfer: https://github.com/noctuid/parinfer-notes
I've been using Parinfer with IntelliJ (Cursive) ever since I started developing Clojure professionally back in 2018. The best thing about Parinfer, or at least the implementation in Cursive, is that it doesn't preclude you from also mixing in some Paredit commands too. When you start out with Clojure/Lisp and you aren't totally used to parenthesis you can just use Parinfer to get editor behaviour similar to developing Python. It removes a major pain point of migrating to a Lisp…
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
- 386
- Total comments
- 114
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 |
|---|---|---|---|---|
| 2016-12-02 | Parinfer | tosh | 3 | 0 |
| 2017-02-28 | Parinfer – Simple Lisp editing | susi22 | 2 | 0 |
| 2017-08-24 | Parinfer | tosh | 1 | 0 |
| 2018-07-28 | Parinfer – Simpler Lisp EditingFirst breakout · Best thread | espeed | 200 | 82 |
| 2020-09-27 | Parinfer | tosh | 1 | 0 |
| 2022-01-01 | Parinfer | tosh | 2 | 0 |
| 2022-02-02 | Parinfer – Simpler Lisp Editing | jasim | 1 | 0 |
| 2022-06-02 | Parinfer – Simpler Lisp Editing | behnamoh | 1 | 0 |
| 2022-09-28 | Parinfer – Simpler Lisp Editing | tosh | 4 | 0 |
| 2022-11-26 | Parinfer | tosh | 1 | 0 |
| 2023-12-08 | Parinfer | tosh | 2 | 0 |
| 2025-01-20 | Parinfer: Simpler Lisp EditingLatest 20+ point return | harperlee | 168 | 32 |