Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #6189

L

Lisper.in

Personal blog · lisper.in · on HN as chaitanyaprogramming

Lisper.in is a personal blog at lisper.in about programming. Since 2014, 12 different Hacker News readers have linked it 21 times, most often “Common Lisp: a tutorial on conditions and restarts”. The last post was in 2022, but the archive is still widely read.

Visit the blog
21mentions?
12HN people?
2014–2022first – last linked?
Links on Hacker News per year · peak 6 in 2022

Too few sampled comments (3) to say how often HN recommends it.?

Why HN links it

HN readers link lisper.in for its Common Lisp material, including a book in progress on writing Common Lisp apps and a reader macros explainer. Comments only cite it as a reference, not judging the writing.

Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Essays on programming, technology and other things

The author on HN?

chaitanya · 390 karma · member since 2009

Essays on lisper.in.

From their public HN profile, which links to this site.

Most-linked posts?

  1. Common Lisp: a tutorial on conditions and restarts
    4 people · 4 mentions · first linked 2017-12-17
  2. Reader Macros in Common Lisp (2014)
    2 people · 3 mentions · first linked 2020-09-02
  3. Writing a natural language date and time parser
    2 people · 2 mentions · first linked 2019-01-22
  4. Reader Macros in Common Lisp
    2 people · 2 mentions · first linked 2015-01-07
  5. Fork-Exec for Python Programmers
    2 people · 2 mentions · first linked 2021-06-18

What Hacker News says?

  1. Do you mean reader macros? Those are used to implement new kinds of syntax within Common Lisp's parser, the READ function. Even standard parts of Common Lisp syntax are defined this way, such as quote (') or backquote (`). For more examples, see http://lisper.in/reader-macros/ .

    Comment linking /reader-macros/

    on “Show HN: Full Stack Lisp – A book in progress about writing Common Lisp apps”
  2. Submitted Reader Macros in Common Lisp (2014) as a story · 93 points

    HN discussion
  3. You can’t, because JavaScript date objects are just timestamps. Here’s what I wrote on this (along with a small library to handle this problem): https://lisper.in/javascript-date

    Comment linking /javascript-date

    on “Day.js – Fast 2kB alternative to Moment.js with the same modern API”
  4. Submitted Reader Macros in Common Lisp as a story · 87 points

    HN discussion
  5. Right! A long time back we came up with a really nice way of validating CSV files using restarts. I wrote a bit about it: http://lisper.in/restarts

    Comment linking /restarts

    on “Error Handling in Node.js”
  6. Submitted Promises and Lisp as a story · 50 points

    HN discussion
  7. Many years ago I wrote about restarts in CL using the example of a CSV parser: https://lisper.in/restarts Fun fact: the restarts based CSV parser was based on some real world work me and a colleague had done for an online travel portal. I wrote about it here: https://www.reddit.com/r/lisp/comments/7k85sf/a_tutorial_on_...

    Comment linking /restarts

    on “Restarts in Common Lisp”
  8. Submitted vfork() is still evil as a story · 5 points

    HN discussion
  9. (While it seems that the project isn’t active) I’m interested not because of the Rust part but because of the more independent part, with plans to implement conditions and restarts [0]. I’ve mentioned a few days ago [1] about the lack of a clean and consistent lisp (in the development sense, not in the core-language-is-tiny sense) with a CL-like REPL-driven development workflow: maybe Clojure with conditions and res…

    Comment linking /restarts

    on “ClojureRS – Clojure interpreter implemented in Rust”
  10. Submitted JavaScript's Date is just a timestamp as a story · 4 points

    HN discussion
  11. Not OP, but: I think that there's a pretty strong case to be made that conditions, implemented in Common Lisp, are the best implementation of "exceptions"...by not actually being exceptions. Conditions (plus restarts) have two advantages over exceptions (as implemented in almost every other language, including Go and C#) and Rust's error system that neither can replicate: they allow you to selectively keep the stack…

    Comment linking /restarts

    on “Rust: Enums to Wrap Multiple Errors”
  12. Submitted Reader Macros in Common Lisp (2014) as a story · 3 points

    HN discussion
  13. Submitted Writing a natural language date and time parser as a story · 3 points

    HN discussion
  14. Submitted Fork-Exec for Python Programmers as a story · 2 points

    HN discussion
  15. Submitted A JSON Reader Macro in Common Lisp as a story · 2 points

    HN discussion
  16. Submitted Writing a natural language date and time parser as a story · 2 points

    HN discussion
  17. Submitted Design, documentation and exploration of REST APIs as a story · 2 points

    HN discussion
  18. Submitted Common Lisp: a tutorial on conditions and restarts as a story · 2 points

    HN discussion
  19. Submitted Fork-Exec for Python Programmers as a story · 1 points

    HN discussion
  20. Submitted Writing a natural language date and time parser as a story · 1 points

    HN discussion
  21. Submitted Using cryptography for tamper-proof election results after close of polling as a story · 1 points

    HN discussion

Search all of HN for lisper.in

Linked by the same people?