Products · Product
Leiningen
Raised as a usability problem by 11 people on Hacker News over 13 years (2010–2022), in 11 threads.
People raised many different problems with Leiningen, but no single problem has yet been raised by 3 people in 3 different months and threads.
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 11 complaints
- Setting up Leiningen, JVM and deps.edn is so difficult and confusing that the user gave up2022-08-03
- Cryptic warnings and JRE mismatch forced downgrading and later re-upgrading Java to fix2017-11-05
- Clojure tooling, especially Leiningen, feels weird and unintuitive to the commenter2017-01-07
- Managing checkouts and multiple nREPLs is a real headache for developers2016-05-13
- No standard way to use a local jar, forcing a workaround with a local Maven repo2014-12-25
- Author can't figure out how to use it; feels clunky and slow2014-04-13
- Leiningen is a terrible piece of software the commenter finds hard to work with2013-05-15
- Setting up encrypted credentials for private repos is a bit of a pain2013-01-21
- Cryptic 'command not found' and JVM trace with no clear cause2011-07-05
- Leiningen won't work on Windows, forcing manual jar downloads and dependency tracing2010-11-05
- Hard to figure out the right config for swank; docs are nonexistent2010-03-23