Frameworks have benefits which can't easily be achieved with documentation. The most obvious to me is that a framework lets you fire up a complete system of carefully curated components in no time. They also let you defer choices until you actually need to care about them.
Because Clojure's libraries are so composable, it seems like a good approach to fill this gap would be "just" a lein project template with an opinionated set of dependencies, a sane and predictable folder hierarchy, and a good Getting Started Guide. A quick clojars search reveals many that might fit that description, but none have very high visibility. -James -- 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
