Re versions: look at the tags, not the branches.  The 1.4.1 branch was 
anomalous, due to needing to get out a bug fix.


On Tuesday, November 11, 2014 2:17:29 PM UTC-6, Aaron wrote:
>
> Hi Adrian,
>
> I'll share some of my experiences.
>
> * Is Clojure CLR production ready?
> Yes, I have been using it in production for about 2 years now.
>
> * Do its version numbers correspond to the core Clojure version numbers? 
>  (would it be fair to say the Java version is the core version)
> It's fair to say that the Java is the core version, but Dave Miller (the 
> ClojureCLR maintainer) does a pretty good job of keeping it up to date with 
> the Java version.
>
> * Is it sensible to think in terms of writing platform independent code in 
> the same way as we do with cljx files in ClojureScript?
> It is feasible if you put the effort into testing and writing the code 
> correctly, but currently I don't think cljx supports ClojureCLR - you'd 
> probably need to add that functionality yourself.
>
> * How good is the Visual Studio support for Clojure?
> I use emacs and *inferior-lisp* and am pretty happy with them so I can't 
> comment on the Visual Studio workflow.
>
> * Does Leiningen work?
> There is Shantanu's lein plugin and I've tried to do a proof of concept 
> "nlein", but there really isn't the equivalent thing in ClojureCLR. I 
> mostly deploy my .clj files as embedded resources in C# DLL's and have C# 
> call into Clojure to bootstrap things. I'm sure other people use other 
> strategies.
>
> * Are there any significant pitfalls to be aware of?
> Not as many libraries are available and you'll have to do a fair amount of 
> groundwork yourself. Startup time is similar to the JVM verison.
>
> Overall, once I got past the initial hurdles, I found the environment to 
> be quite stable and a huge productivity boost. I would definitely recommend 
> ClojureCLR for projects with a big existing .NET code base. For new 
> projects, I do usually go with JVM Clojure mainly for access to more 
> libraries and IDE's. At the time when I started using ClojureCLR our team 
> was heavily invested in .NET so it made a lot of sense and was definitely 
> well worth it...
>
> Be sure to check out the ClojureCLR google group: 
> https://groups.google.com/forum/#!forum/clojure-clr
>
>
> On Tuesday, November 11, 2014 10:38:58 AM UTC-5, Adrian Mowat wrote:
>>
>> Hi All,
>>
>> We are using Clojure on the JVM but one of our .Net developers has asked 
>> me whether I have considered using it on the CLR.  I haven't tried doing it 
>> so I wondered if anyone can share any experiences using Clojure on the CLR? 
>>  A quick google search suggests the project is still active but not 
>> especially vibrant (current version 1.4, last commit 24 days ago) but maybe 
>> that's unfair.
>>
>> I'm broadly interested in the following...
>>
>> * Is Clojure CLR production ready?
>> * Do its version numbers correspond to the core Clojure version numbers? 
>>  (would it be fair to say the Java version is the core version)
>> * Is it sensible to think in terms of writing platform independent code 
>> in the same way as we do with cljx files in ClojureScript?
>> * How good is the Visual Studio support for Clojure?
>> * Does Leiningen work?
>> * Are there any significant pitfalls to be aware of?
>>
>> Any other comments would be greatly appreciated.
>>
>> Many Thanks
>>
>> Adrian
>>
>>
>>
>>
>>
>>

-- 
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.

Reply via email to