Products · Product
Lisp
Raised as a usability problem by 97 people on Hacker News over 20 years (2007–2026), in 93 threads.
Every issue, all time, most people first
Nested parentheses make Lisp code hard to read and editUnreviewed
20072026- Struggled to match parentheses and wasted a lot of time early on2026-09-28
- Lisp code is hard to read, even the author's own old code2026-07-17
- Parenthesis syntax is horrible to read and edit2026-06-02
Macro-heavy code hides what actually happens from readersUnreviewed
20072026- Macros look like function calls and everything looks alike, so code is hard to read2022-09-25
- Macro-heavy code becomes obscure, so readers can't tell what's really happening2021-08-28
- Macros become undocumented personal languages nobody else can understand or use2021-08-02
Newcomers struggle to work out which Lisp download to getUnreviewed
20072026- Getting a working Lisp dev environment takes half a day with many convoluted steps2021-08-14
- Setting up a Lisp environment takes a day, especially on Windows2015-01-31
- Newbies struggle to figure out which Lisp download to get, taking too long searching2008-05-30
Getting Lisp running requires learning Emacs or the JVM firstUnreviewed
20072026- Using the Lisp REPL forces beginners to learn Emacs first2024-03-02
- Couldn't get comfortable running Lisp from within Vim; integration not as good as promised2023-07-27
- Getting a Lisp running means learning Emacs or messing with the JVM first2009-09-16
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 50 complaints
- Struggled to match parentheses and wasted a lot of time early on2026-09-28
- Each variable binding adds another nested block, making code hard to follow and read2026-09-28
- Lisp code is hard to read, even the author's own old code2026-07-17
- Lisp's bracket syntax is hard to read and edit, especially long numerical expressions2026-06-02
- Parenthesis syntax is horrible to read and edit2026-06-02
- Can't tell which functions a type supports without already knowing them2026-05-24
- Parentheses need Shift on modern keyboards, making Lisp code awkward to type2026-03-12
- Impossible to track which method runs in deep, overridden method combination hierarchies2025-11-16
- Parenthesis-heavy syntax is brain-hostile and makes reading and writing harder2025-07-30
- Stepping into low-debug functions is impossible or lands in decompiled source2025-04-24
- Hard to find useful operations when first exploring a Lisp library2025-04-11
- Deep nesting makes code hard to read and needs too much screen space2025-04-10
- Lisp's prefix syntax is off-putting, with no infix arithmetic for basic math2025-02-19
- Tiny-machine Lisps had crashes and lacked a usable programming environment2025-01-11
- Unhelpful error messages make matching parentheses errors take 30 minutes to debug2025-01-07
- Lisp's parenthesis-heavy syntax adds visual noise, making code harder to inspect2024-06-17
- Using the Lisp REPL forces beginners to learn Emacs first2024-03-02
- Parenthesis-heavy syntax is hard to read at a glance and awkward to edit2024-02-12
- Hard to set breakpoints on nested expressions and step through them, unlike Visual Studio2024-01-25
- Library docs are inconsistent across projects and sometimes hard to find2024-01-25
- Page is hard to read on mobile devices2023-08-19
- Setting up a REPL-editor integration in Vim is hard, and the breakloop is confusing2023-07-27
- Couldn't get comfortable running Lisp from within Vim; integration not as good as promised2023-07-27
- Commenter cannot get past Lisp's syntax and gives up learning it2023-06-26
- Hard for beginners to find answers because knowledge lives in unwritten IRC chats2023-05-09
- Editing Lisp code is hard without special tooling to manage the parentheses2023-02-02
- Documentation says NIL is an empty list, which misleads readers about its actual behavior2022-12-17
- Can't tell whether a call is a function or macro without looking it up2022-11-05
- Macros look like function calls and everything looks alike, so code is hard to read2022-09-25
- Forces programmers to attend to irrelevant nesting of function bodies and control constructs2022-08-29
- Light blue links on yellow background are almost impossible to read2022-06-02
- Setup information is missing, and knowledge is scattered across many small outdated sites2022-04-30
- Lisp code looks totally unreadable to the commenter2022-04-28
- Spends a lot of time figuring out the actual type of a function's result2021-11-12
- Nested parentheses make Lisp code hard to read and edit2021-09-01
- Macro-heavy code becomes obscure, so readers can't tell what's really happening2021-08-28
- Getting a working Lisp dev environment takes half a day with many convoluted steps2021-08-14
- Emacs takes about a year to learn, so beginners struggle to get productive2021-08-02
- Macros become undocumented personal languages nobody else can understand or use2021-08-02
- Parameters are hard to tell apart from the function name, taking too long to parse2021-06-10
- Heavy context sensitivity and text-heavy syntax make code hard for humans to read2020-10-26
- Nested destructuring-bind forms are hard to read and write2020-10-02
- Programs lack a main entry point, so starting one by calling a form is unintuitive2020-08-08
- Code structure hard for humans to parse, since everything looks like uniform text2019-09-10
- Editing s-expressions without Paredit-style help is a nightmare for the user2019-08-08
- Tooling and UX are rough; simple tasks like exporting binaries often fail2019-07-16
- Lisp code is hard to read because symbols could be variables, functions or operators2019-07-07
- Macro transformation makes compiler and programmer communication hard, hurting tooling and error messages2019-06-24
- Hard to track nesting depth of many parentheses when using a screen reader2018-11-09
- Difficulty ramps up too quickly, making the section hard to process2018-11-01