best practice with forked libraries

Say there's a dependency that I fork and add some features I need for my team's project. I can use my fork locally with lein install no problem, and so can others *if* they clone my fork and do the same. It would be more convenient if I could publish my fork to Clojars and depend on that, and

ClojureExchange ticket to give away

Hey, I have bought a ClojureExchange [1] ticket right after last years conference, but I will not be able to participate this year. ClojureExchange takes place in London from Dec. 3 - Dec. 5. I would primarily like to give the ticket to someone who would otherwise not be able to participate,

Re: ClojureExchange ticket to give away

The ticket is gone. Am Dienstag, 17. November 2015 11:35:36 UTC+1 schrieb Torsten Uhlmann: > > Hey, > > I have bought a ClojureExchange [1] ticket right after last years > conference, but I will not be able to participate this year. > > ClojureExchange takes place in London from Dec. 3 - Dec.

Re: best practice with forked libraries

On 17 November 2015 at 13:21, Bobby Bobble wrote: > Say there's a dependency that I fork and add some features I need for my > team's project. I can use my fork locally with lein install no problem, and > so can others *if* they clone my fork and do the same. It would be more >

Re: best practice with forked libraries

In addition to Ray's response (which I would also suggest), I'd encourage you to reach out to the project maintainer/author with your additions - it's always nice to see how your project is being used and the shortcomings that others are hacking around. Cheers, Paul -- You received this

Is there a "State of Clojure 2015" coming?

Yes! It's basically ready to go but I ran out of time to post it before the conj. coming soon -- 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

Is there a "State of Clojure 2015" coming?

One of the topics I had hoped to see coming out of the Conj is a 2015 update to the State of Clojure survey. Is the survey something that is in the plans for 2015? Thanks! -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send

Is there a "State of Clojure 2015" coming?

Outstanding! thank you for the effort, Alex. -- 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

Re: ClassNotFoundException: clojure.lang.AFunction on OS X

It appears this is down to JavaFX. Having skipped the javaFX part, the system runs fine. On Tuesday, November 17, 2015 at 8:53:50 AM UTC, Phil Segal wrote: > > Hi > > I have found the cause this morning. The ContextClassLoader on the > currentthread was null. I managed to work around this by

Re: Poor parallelization performance across 18 cores (but not 4)

Could you also show how you are running these functions in parallel and time them ? The way you start the functions can have as much impact as the functions themselves. Regards, Niels On Tuesday, November 17, 2015 at 6:38:39 AM UTC+1, David Iba wrote: > > I have functions f1 and f2 below, and

Re: ClassNotFoundException: clojure.lang.AFunction on OS X

Hi I have found the cause this morning. The ContextClassLoader on the currentthread was null. I managed to work around this by checking for null and then setting it as the SystemClassLoader if needed. I am using lein 2.5.3, java 1.8.0_65. The ClassLoader issue only occurs on Mac, but there

Re: Poor parallelization performance across 18 cores (but not 4)

Andy: Interesting. Thanks for educating me on the fact that atom swap's don't use the STM. Your theory seems plausible... I will try those tests next time I launch the 18-core instance, but yeah, not sure how illuminating the results will be. Niels: along the lines of this (so that each

Re: Poor parallelization performance across 18 cores (but not 4)

correction: that "do" should be a "doall". (My actual test code was a bit different, but each run printed some info when it started so it doesn't have to do with delayed evaluation of lazy seq's or anything). On Tuesday, November 17, 2015 at 6:49:16 PM UTC+9, David Iba wrote: > > Andy:

Re: best practice with forked libraries

A lot of time ago I wrote the following tutorial on this topic. https://github.com/magomimmo/modern-cljs/blob/master/doc/tutorial-19.md HIH mimmo > On 17 Nov 2015, at 20:48, Paul deGrandis

Re: Poor parallelization performance across 18 cores (but not 4)

David, you say "Based on jvisualvm monitoring, doesn't seem to be GC-related". What is jvisualvm showing you related to GC and/or memory allocation when you tried the 18-core version with 18 threads in the same process? Even memory allocation could become a point of contention, depending upon