It is, as you're pointing out, at this time, a very thin wrapper over what your example shows. It provides the ability for the code to look more like typical Ruby function calls. Thanks for helping to define that.
For me it is to leverage our existing testing tools: Rspec and Cucumber to test our Clojure libraries. The team I'm on already has a lot of experience with those two testing tools, and our analysts and QA personnel are able to understand tests written in those two tools. My experience has not been the same with JUnit and the Clojure based testing libraries -- developers are fine with it, but non-devs tend to provide very little input for unit or clj based tests. I think the imperative nature of those test are too dense or they say too much about how rather than what is being tested.
Comments
What does this do that you can't do by calling native java code from JRuby?
All Clojure code can be called from Java by doing (pseudo-code):
It is, as you're pointing out, at this time, a very thin wrapper over what your example shows. It provides the ability for the code to look more like typical Ruby function calls. Thanks for helping to define that.
Thankyou. This is going to be very useful to me very soon.
You're welcome, what I really wanted was to be able to use rspec to test my clojure libs, and now I can :)
Ill be anxious to hear your experiences with it
out of curiosity, why is this useful? what kind of functionality do you need in clojure that you can't find in jruby?
Specifically, the ability to run Clojure code. :)
I want to make it possible to write plugins in Clojure for http://redcareditor.com It should be pretty easy to do, this will make it even easier.
You should now be able to write most of your app logic in Clojure, and use Monkeybars for a cross-platform Swing GUI.
See http://kenai.com/projects/monkeybars
For me it is to leverage our existing testing tools: Rspec and Cucumber to test our Clojure libraries. The team I'm on already has a lot of experience with those two testing tools, and our analysts and QA personnel are able to understand tests written in those two tools. My experience has not been the same with JUnit and the Clojure based testing libraries -- developers are fine with it, but non-devs tend to provide very little input for unit or clj based tests. I think the imperative nature of those test are too dense or they say too much about how rather than what is being tested.