Adding a vote for Potemkin's import-vars. Also, I've been using Stuart's component approach for almost a year in a half-dozen projects and it's real value is having a consistent architecture - I find projects that don't use it are likely to invent their own ad-hoc, informally-specified alternative. We've also used the library in a project developed by ~10 engineers and it's scaled up well.
I think the best resource for learning about component is one of Stuart's talks: https://www.youtube.com/watch?v=13cmHf_kt-Q I've also talked about many of the underlying details and subtleties of the approach, and how you would recreate it from the ground up. See here for the recording: https://skillsmatter.com/skillscasts/5820-components-with-clojure On Thursday, 30 October 2014 02:52:46 UTC, jaju wrote: > > I find Potemkin's import-vars [https://github.com/ztellman/potemkin] too > a very neat addition to one's toolbox. Allows one to keep a clean > code-layout. > I haven't used the other parts to comment on them. > > Best, > Ravindra > > On Thu, Oct 30, 2014 at 5:44 AM, Daniel Szmulewicz <daniel.s...@gmail.com > <javascript:>> wrote: > >> If you'll follow James Reeves' recommendations (which you should), you >> might want to have a look at System, a library that streamlines the process >> of setting up components. This is the first step I take with any Clojure >> project. >> >> https://github.com/danielsz/system >> >> Its sole dependencies are Components by Stuart Sierra and reloaded.repl >> by James Reeves. >> >> On Monday, October 27, 2014 3:42:27 PM UTC+2, Colin Yates wrote: >>> >>> Thanks all. >>> >>> Just managed to wire in clojurescript.test into my lein build - woot :). >>> >>> On Monday, October 27, 2014 1:38:02 PM UTC, James Reeves wrote: >>>> >>>> I've gotten on well with using Component >>>> <https://github.com/stuartsierra/component> for managing the >>>> high-level I/O dependencies of my application. >>>> >>>> There's also Ring-Defaults >>>> <https://github.com/ring-clojure/ring-defaults>, which provides >>>> sensible and customisable default middleware settings. >>>> >>>> - James >>>> >>>> On 27 October 2014 11:07, Colin Yates <colin...@gmail.com> wrote: >>>> >>>>> About to embark on a new project and interested in "wish I knew >>>>> this"/"wish I had used this" type sentiments. An extension of this >>>>> splendid >>>>> article: http://blog.mattgauger.com/blog/2014/09/15/clojure-code- >>>>> quality-tools/. Any others? >>>>> >>>>> For context, this is going to be a non-trivial SPA using clojurescript >>>>> supported by a Clojure backend (https://groups.google.com/d/ >>>>> topic/clojurescript/9cDFfAGsDE4/discussion) >>>>> >>>>> In addition to the tips I found in the article I am also planning on >>>>> using core.typed, primarily to address the "anyone remember what this >>>>> data >>>>> structure looked like?" 12 month maintenance risk. I did look at >>>>> schematic >>>>> but I like the extra enforcement core.typed gives. >>>>> >>>>> On a side note, answering this question from google alone is >>>>> non-trivial. We, as a community have reached that point where there are >>>>> so >>>>> many (good, but overlapping and sometimes contradictory) good next steps >>>>> it >>>>> is easy to be paralysed by choice. A few more "authorized" (whatever that >>>>> means) "prescriptions" wouldn't go amiss. Not sure what the answer is, >>>>> merely raising the flag. >>>>> >>>>> So, what tips/techniques/XYZ do you wish you had started with? >>>>> >>>>> Thanks! >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Clojure" group. >>>>> To post to this group, send email to clo...@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+u...@googlegroups.com >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/clojure?hl=en >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Clojure" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to clojure+u...@googlegroups.com. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clo...@googlegroups.com >> <javascript:> >> Note that posts from new members are moderated - please be patient with >> your first post. >> To unsubscribe from this group, send email to >> clojure+u...@googlegroups.com <javascript:> >> For more options, visit this group at >> http://groups.google.com/group/clojure?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Clojure" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to clojure+u...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
