When i started clojure programming it was much better for interactive lisp development. I haven't tried vim with fireplace in a long time for clojure development but it's still a nice tool. I tried it back before vim had async calls which is one thing that made it a pain. I think the reason emacs is better for lisp development is because it already had a lot of the necessary concepts for interactive development built in for emacs lisp (eval-last-sexp for example). Many lisp users just use emacs so a lot of the great tooling like Cider was developed for emacs.
I've also found emacs to be great for common lisp and hy.
Yeah. Navigation is fine. Cider uses the running instance of your application to do navigation and code completion. For editing you have tools like parinfer and smartparens for lisps. I believe vim has ports of those which work well.
When i started clojure programming it was much better for interactive lisp development. I haven't tried vim with fireplace in a long time for clojure development but it's still a nice tool. I tried it back before vim had async calls which is one thing that made it a pain. I think the reason emacs is better for lisp development is because it already had a lot of the necessary concepts for interactive development built in for emacs lisp (
eval-last-sexpfor example). Many lisp users just use emacs so a lot of the great tooling like Cider was developed for emacs.I've also found emacs to be great for common lisp and hy.
Ah, this makes sense. I was thinking about code editing + navigation, but yeah, I can see how emacs would be better for REPL/interactive usage.
Yeah. Navigation is fine. Cider uses the running instance of your application to do navigation and code completion. For editing you have tools like parinfer and smartparens for lisps. I believe vim has ports of those which work well.