One tool that got some love at one point was Cusp, a Lisp plugin for Emacs. Unfortunately, as I note here[1], it's been unloved for some time.
One tool that got some love at one point was Cusp, a Lisp plugin for Emacs. Unfortunately, as I note here[1], it's been unloved for some time.
I no longer feel lost in Emacs. I was able to anchor it to my background with AutoCad - and there are huge architectural similarities between Emacs and pre-Windows versions of AutoCad. Both have a command driven interface.
The difficulty with the Emacs tutorial is that it is written around social mores. Thus it teaches the shortcuts which distinguish emacs community insiders from outsiders [1]. Yes, no sane experienced Emacs user will type:
M-x next-line
But it turns: C-n
from cryptic into mnemonic.You know, Sublime Text integration might be possible. But Eclipse is, as near as I can tell, the canonical mainstream GUI IDE. I think getting Swank(SLIME) integrated into a mainstream IDE would add to Common Lisp's usability for the non-command-line crowd by leaps and bounds.
I see the computing world as fundamentally bimodal: people trend hard towards GUIs and mice or they trend hard towards CLIs and keyboards. Common Lisp's development environment is built by and for the second crowd. You might call them... hackers. :-) But I would dearly love to see the non-hacker computing world walk in the wonders of Lisp. I've attempted to teach several people Lisp, and the development environment is, hands down, the major stumbling point (after the parentheses whining is finished with). This is a major barrier to getting people onboarded. I suppose that means I should try to get Cusp/lispdev compiling this weekend and see what state its in. :-)
Other barriers include no modern GUI library[1]; no popular webapp framework[2], no single point of contact for the language, and a lack of a flagship thing to raise the flag around (Ruby/Rails, Python/NumPy|Django, Clojure/not-java, etc).
[1] The libraries that exist are fairly thin bindings over QT, SDL, and TK. They are far behind the sleek usability of, say, Clojure's seesaw or the even clunkiness of C# autogenerated code.
[2] Clack and children are getting there