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 · #11669

D

Dan's Musings

Personal blog · blog.djhaskin.com/blogprogramming

Dan's Musings is a personal blog at blog.djhaskin.com about programming. Since 2024, 6 different Hacker News readers have linked it 17 times, most often “Experience Report Using VS Code and Alive to Write Common Lisp”. It is still writing: the last post was on 2026-08-14, and you can follow it by feed.

Visit the blog
17mentions?
6HN people?
2024–2026first – last linked?
Links on Hacker News per year · peak 7 in 2024

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

Why HN links it

Dan's Musings, linked for posts about using Common Lisp: an experience report on VS Code for Lisp, and a guide to building executables. Comments cite them as sources, not as recommendations.

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.

Don't take it too seriously.

Most-linked posts?

  1. Experience Report Using VS Code and Alive to Write Common Lisp
    3 people · 3 mentions · first linked 2024-09-11
  2. Release Common Lisp on Your First Day (2023)
    2 people · 2 mentions · first linked 2025-01-12

What Hacker News says?

  1. > Let's make CRLF one less thing that your grandchildren need to know about or worry about. The struggle is real, the problem is real. Parents, teach your kids to use .gitattribute files[1]. While you're at it, teach them to hate byte order marks[2]. 1: https://stackoverflow.com/questions/73086622/is-a-gitattribu... 2: https://blog.djhaskin.com/blog/byte-order-marks-must-diemd/

    Comment linking /blog/byte-order-marks-must-diemd/

    on “CRLF is obsolete and should be abolished”
  2. Submitted Why I Chose Common Lisp as a story · 363 points

    HN discussion
  3. Not really. OP needs to build executables. It is documented here: https://blog.djhaskin.com/blog/release-common-lisp-on-your-f...

    Comment linking /blog/release-common-lisp-on-your-first-day/

    on “Why I Chose Common Lisp”
  4. Submitted Mutt on Windows Without WSL as a story · 101 points

    HN discussion
  5. Maybe you tried some time ago? This experience report concludes by "all in all, a great rig": https://blog.djhaskin.com/blog/experience-report-using-vs-co... > The usage experience was very ergonomic, much more ergonomic than I'm used to with my personal CL set-up. Still, the inability to inspect stack frame variables would bother me, personally. I don't use them, but I'd recommend Pulsar's SLIMA over the VSCode plu…

    Comment linking /blog/experience-report-using-vs-code-alive-to-write-common-lisp/

    on “Why I Program in Lisp”
  6. Submitted Common Lisp Community Survey 2024 Results as a story · 98 points

    HN discussion
  7. I just do it in vim and tmux (it used to be screen): https://blog.djhaskin.com/blog/developing-common-lisp-using-... This works real well. I honestly don't see the point of slime, it feels like it was written so that people didn't have to use the terminal, but the terminal works just fine for me. I even wrote a :make plugin for it, which works well enough: https://git.sr.ht/~skin/roswell-sbcl.vim

    Comment linking /blog/developing-common-lisp-using-gnu-screen-rlwrap-and-vim/

    on “A Road to Common Lisp (2018)”
  8. Submitted Common Data Structures in Common Lisp as a story · 49 points

    HN discussion
  9. Yeah, I mean there is some support for various editors ( https://lispcookbook.github.io/cl-cookbook/editor-support.ht... ) including VS Code ( https://lispcookbook.github.io/cl-cookbook/vscode-alive.html ), but it's kind of rough ( https://blog.djhaskin.com/blog/experience-report-using-vs-co... ) and not exactly feature-complete with the emacs experience, plus you're still left having to figure out how to install an…

    Comment linking /blog/experience-report-using-vs-code-alive-to-write-common-lisp/

    on “Mine, an IDE for Coalton and Common Lisp”
  10. Submitted Benchmarking the CLOS as a story · 10 points

    HN discussion
  11. Submitted Experience Report Using VS Code and Alive to Write Common Lisp as a story · 3 points

    HN discussion
  12. Submitted The AI Curse (Vis the Lisp Curse) as a story · 2 points

    HN discussion
  13. Submitted Emacs Users: I'm Okay, I Promise (2022) as a story · 2 points

    HN discussion
  14. Submitted Muxxy: Like Slime, for AI and Tmux as a story · 1 points

    HN discussion
  15. Submitted Pi Is Bad; Or, The Positive Effects of Friction in Automated Development as a story · 1 points

    HN discussion
  16. Submitted Writing Lisp Is AI Resistant and I'm Sad as a story · 1 points

    HN discussion
  17. Submitted Release Common Lisp on Your First Day (2023) as a story · 1 points

    HN discussion

Search all of HN for blog.djhaskin.com

Linked by the same people?