On Jun 30, 10:17 am, Sean Allen <s...@monkeysnatchbanana.com> wrote: > The larger the clojure community gets, the more you should be prepared > for those dogs then.
To put it more bluntly - the day that clojure no longer interoperates smoothly with java is the day it becomes useless to me. I'm all for hiding the guts from beginners but it's going to be a good long while before you can actually get anything done with clojure without directly interfacing with java. For example, I'm using clojure for two things at work: replicating data between a sybase and oracle DB and syncing data from ldap to an xml-rpc client and a proprietary calendaring solution with it's own java api. I can defend my use of clojure here because it's actually better than python at this - faster and with more mature drivers and able to invoke java apis directly. My code is full of direct calls to various java methods, invocations of java constructors etc. Without clojure's excellent java support it would be off the table as an option for this project and without decent knowledge of java I wouldn't be able to use it. I suspect most of the non-trival tasks for which other people are using clojure rely on a number of java libraries for which no clojure wrapper exists and I don't think is likely to change soon or even that we *should* wrap everything. I don't know what the implementation plans are exactly for clojure-in- clojure but abandoning the JVM would be extremely unwise. -- 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
