On Sat, Jul 30, 2011 at 5:27 PM, Mark Engelberg <mark.engelb...@gmail.com> wrote: > I guess what I'm > thinking of is that 95% of the time when I go to start something new, > it ends up being for a short-lived task
Sounds like both Phil and I tackle that by having one or more scratch projects that we just add new dependencies to as needed. Anything that becomes longer-lived is "promoted" into its own project if/when it makes sense. > I'm not sure how well that would work > with the way I have things organized, and with my source control, but > it's something I can look into. I guess our definitions of "one-off" might be different? If I'm just doing a one-off experiment in the REPL, it's not likely to end up under version control. If it's long-lived enough to go under version control, it's probably worth a project :) I definitely agree that compared to certain scripting languages, there's more ceremony with Clojure (or any other JVM language) because you can't just drop a source file in any old folder and run it. If you don't mind a compilation step, ClojureScript -> JavaScript and then running it with Node.js allows you to have scripts "anywhere" and easily run them... -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ World Singles, LLC. -- http://worldsingles.com/ Railo Technologies, Inc. -- http://www.getrailo.com/ "Perfection is the enemy of the good." -- Gustave Flaubert, French realist novelist (1821-1880) -- 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 Note that posts from new members are moderated - please be patient with your first post. 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
