Products · Product
Nim
Raised as a usability problem by 58 people on Hacker News over 13 years (2014–2026), in 53 threads.
No issue was raised by at least 3 people in 3 threads this year.
Every issue, all time, most people first
Identifier search ignores underscores and case variantsUnreviewed
20142026- Searching for identifiers is hard because underscores and case variants are ignored2023-03-31
- Unclear whether camelCase and snake_case identifiers collide, and hard to grep for them2022-05-05
- Underscore and case variants are the same identifier, so grep and search fail and code is harder to read2021-12-17
Tutorials lacking and examples stop at trivial programsUnreviewed
20142026- Found the language confusing to learn because documentation was sparse and the forum unwelcoming to newcomers2021-04-14
- Had to dig through old forum posts to learn basic language features2017-05-07
- Language is so large and feature-dense that it is hard to learn and figure out2016-06-23
Compiler error messages are unhelpful for diagnosing problemsUnreviewed
20142026- Compiler crashes, confusing error messages, and LSP hangs2026-05-26
- Compiler error messages are terrible and unhelpful for diagnosing problems2020-07-18
- Compiler errors are arcane, especially with generics or C compilation2019-10-30
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
- Compiler crashes, confusing error messages, and LSP hangs2026-05-26
- Debugging is pretty bad, forcing reliance on printf debugging2025-11-30
- Many competing options with no clear way to choose, learned only from forum posts2025-11-01
- Whitespace-significant syntax is unwieldy, especially when copy-pasting code or config2025-08-28
- Hard to tell where an imported function comes from2025-03-04
- Unary minus binds tighter than exponentiation, so -2^2 gives 4, which is unintuitive2024-09-14
- Standard install lacks a beginner-friendly editor, so users must configure everything themselves2024-09-06
- Basic editor features in the VSCode extension are buggy and missing IDE conveniences2024-07-22
- Docs are hard to navigate, hard to find things, and examples are convoluted2024-02-24
- Tooling chokes on bad syntax, forcing restarts, and method docs only appear when used correctly2023-10-03
- Text and code samples are hard to read at default zoom due to small font and low contrast2023-08-03
- Nim installers were broken, and updating one stopped it working2023-06-26
- Can't just install a plugin and run; must configure stuff and debugger is unclear2023-03-31
- Searching for identifiers is hard because underscores and case variants are ignored2023-03-31
- Must remember whitespace in backwards-indexed slices or the code crashes; some slice forms error2023-02-12
- Documentation is poor and unpolished, hard to learn from2022-11-25
- Error messages are misleading red herrings that waste debugging time2022-11-11
- Unclear whether camelCase and snake_case identifiers collide, and hard to grep for them2022-05-05
- Unclear when to use ref versus plain object types, confusing to learn2022-02-27
- Underscore and case variants are the same identifier, so grep and search fail and code is harder to read2021-12-17
- Lack of IDE support made learning the language very painful2021-10-19
- Symbolic names are obscure, hard to infer, pronounce, and search for2021-10-19
- Case-insensitive rules are complicated to mentally compute and make searching identifiers harder2021-09-25
- Every page takes seconds to load, even when opened in background tabs2021-08-27
- Found the language confusing to learn because documentation was sparse and the forum unwelcoming to newcomers2021-04-14
- Macros change syntax on import, making the language hard to learn2021-03-11
- Docs aren't good enough, so looking up how to do something is hard2021-03-11
- Can't reliably spell function names even when knowing how to use them2021-02-24
- Indentation-based blocks are hard to parse and easy to mis-indent2021-01-01
- Implicit member resolution makes code hard to read and understand at a glance2020-12-23
- Curly braces draw the eye and confuse code navigation and understanding2020-10-22
- Pragmas on procedure declarations create long lines and awkward line breaks2020-10-21
- Docs throw everything at beginners at once, overwhelming them with no progression2020-08-16
- Compiler error messages are terrible and unhelpful for diagnosing problems2020-07-18
- Developer finds how imports work in Nim frustrating for header-like files2020-04-04
- Compiler errors are arcane, especially with generics or C compilation2019-10-30
- Nim's docs were really bad for the commenter2019-10-30
- Searching plain text for a variable doesn't find it, since identifiers are style-insensitive2018-11-29
- Documentation is sparse, so the user had to read library source code to work things out2018-09-27
- Readers skimming headings wrongly conclude they must manually configure PATH and hunt DLLs2018-08-28
- Case-dependent identifier matching sounds confusing to the programmer2018-06-13
- Beginner hits many conceptual walls, frustrations mounting while learning Nim2017-10-29
- Hard to remember where the export asterisk goes, which feels illogical2017-10-28
- Had to dig through old forum posts to learn basic language features2017-05-07
- Manual page is not accessible in a good way on phone2017-04-19
- Can't find a quick start guide to run code after installing2017-04-19
- Hard to get a Nim GUI package working after fiddling with dependencies2017-01-19
- Macros touch undocumented internals, so finding the cause of problems takes time2017-01-09
- Documentation quality is poor and obscure problems are hard to search for answers2017-01-09
- Templating system feels more confusing and clumsy than Lisp's equivalent2016-10-01