4 ms·
Tooling around Java (e.g. Eclipse) has developed significantly since the time this article was written. If you're working in programs where the system is too bi
by enduser 13y ago
Tooling around Java (e.g. Eclipse) has developed significantly since the time this article was written. If you're working in programs where the system is too big to fit in your mind, good tooling certainly helps. Lisp is especially powerful for programmers who are able to work with large and complex mental models of systems.
and
Debugging Lisp in Lisp is far superior (easier) compared to debugging Lisp in Java (which is what you get when you use Clojure). Clojure has been getting a lot of press as being the rebirth of Lisp, and it includes some useful paradigms in the core language, but it is woefully incomplete as a full Lisp development system when compared to mature Common Lisp implementations.
- peter-fogg 13y agoOut of curiosity, what do you see as the difference between Common Lisp debugging and Clojure debugging? I'm mostly experienced with Clojure (my CL code consists of a few trivial programs), but it seems like Lisp in the right environment (Emacs, paredit, SLIME/nrepl) is a joy regardless of which Lisp.