Jan Rychter <j...@rychter.com> writes: > Let people use whatever they want, try their stuff from the command-line > and REPL, and once they get used to it, move up to Emacs and SLIME.
Agreed. > I agree there are superficial barriers, though. I believe it is very > important for Clojure to: > > a) have an build process that results in something that you can run > from your command line right away (without learning about the syntax > of java command-line arguments), This was one of the most disorienting things I encountered when starting with clojure. I'm used to codebases providing a bin/ directory or at least a shell script to start from. It wouldn't be so bad if the java CLI launcher were any good, but it's pretty lousy. I've been looking at hashdot, (http://hashdot.sourceforge.net/) and it seems to address the weaknesses of the java command in a pretty intuitive way that makes it seem like a first-class citizen in Unix. It lets you write shebang-savvy scripts, and it sets the process names so you get something reasonable showing up in ps and top instead of the jumble of alphanumerics that the jvm shows by default. So far I've only used it with JRuby, but it's meant to work with any JVM-hosted language. It seems like it addresses a pain point that is particularly onerous with Clojure. -Phil --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
