IMO there is little value in big dependency hair-balls and gui tools leakily abstracting devop taks.
There is, however, value in curated sets of independent libriaries that work well together. Also in having declarative syntax available for common tasks. Still IMO, Clojure's web story is still somewhat lacking on those. More specifically in in environment integration, since ring does a great job for binding application components. Lately I'm trying to push all code that deals with environment and project configuration into leiningen plugins. I think together with project templates, that can be a great way to get more of the convenience of your classic framework. kind regards -- 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
