Picture of stu

Participate in a Clojure Case Study

  • Posted By Stuart Halloway on October 20, 2008

Relevance is seeking a partner for a Clojure case study. Here's the deal:

  • You have a small but non-trivial application slated for development in Java. (Let's say $20K - $50K budget).
  • Relevance builds your application in Java, per your budget.
  • Relevance builds a second version of the application in parallel, for free, in Clojure.
  • You own the Intellectual Property for both the Java and Clojure versions.
  • Relevance produces a case study comparing the two implementations. The case study cites extensively from both codebases.
  • Relevance releases the case study under a Creative Commons License.

If you are interested, give us a call at 919.442.3030, or email stu at thinkrelevance.com.

For more about Clojure, check out the home page and these video introductions. For more about Relevance, check out our approach and our list of satisfied clients.

[10/21/2008: updated to make clear that the two versions will be developed in parallel, not in sequence.]

Comments
  1. Daniel SpiewakOctober 20, 2008 @ 06:46 PM

    Neat idea! Wish I had a project to hire you for…

    I’m looking forward to the results.

  2. FogusOctober 20, 2008 @ 07:27 PM

    I have been looking for a way to sell Clojure to my team… you may have done it for me.

    -m

  3. RechnungOctober 20, 2008 @ 08:25 PM

    When you choose one write here about this application. I am really interested in.

  4. jherberOctober 21, 2008 @ 12:27 PM

    Writing in Java first and then Closure will bias your results, unless you use two independent implementation teams, and the latter is not allowed to see the former’s work. In effect, both of them must produce independent results sharing only specifications.

    You should also sign up for a maintenance contract on said code bases, so phase II can look at the cost of maintenance and feature add.

    And if you want to make things really interesting, you should have another team produce a solution in Scala.

  5. Stuart HallowayOctober 21, 2008 @ 01:51 PM

    jherber: all good points. Once we select a partner we will hash out the details, and publish the plan in advance.

    At some point we’ll have to compromise. Another version in Scala would be great. And why not two more in F# and Haskell? We’ll have to draw a line somewhere. :-)