VimClojure Winding Down

In On the state of VimClojure, Meikel Brandmeyer recommends using Tim Pope's foreplay.vim and Sung Pae's vim-clojure-static as an alternative to VimClojure, because he intends to step back from the project:

"That all said I still have some ideas on Clojure tooling I want to experiment with. So I will continue to work on the interactive part of VimClojure, but things will probably move in a much slower pace compared to the other projects."

So it's not exactly time to say goodbye to VimClojure, but the author himself is recommending moving to other projects.

The ensuing discussion on the state of VimClojure is positive, and some posters have expressed an interest in keeping the vimclojure group alive for discussions relating to Vim and Clojure in general.

If you're not a Lisp developer, it's hard to appreciate the importance of VimClojure. It stems from Emacs SLIME. To understand why SLIME is useful, read Like Slime, for Vim by Jonathan Palardy:

"Let me present the dilemma another way: irb [a Ruby REPL] is great to get answers quick but it is also temporary because you know nothing you do in irb will be saved. However, the moment you start living in a text editor, you give up a lot of the power of REPL. Or, at least, your REPL becomes 10 seconds instead of 1 second. That changes the way you work. And that explains why Slime exists."

It's natural that Clojure developers may gravitate to Emacs, but there are several Vim plugins that help integrate Vim's workflow with interactive programs. There's a Getting Started with Vim page in clojure.org's documentation where several people have posted useful links to projects like Conque. Also, Vim Pipe is a more recently developed plugin that should work well with a Clojure shell.

blog comments powered by Disqus