On Thursday, June 6, 2013 1:55:13 AM UTC-5, Zed Becker wrote:
>
> Why do the languages running on the CLR (ironRuby, ironPython, ironScheme, 
> ScalaCLR) do not get to live long enough in the sunshine, whereas same 
> languages get embraced by the Java runtime, and live in the limelight? 
>

Many respondents have dealt with this question, in detail.   I can confirm 
that some of the CLR extras (structs, reified generics, ...)  complicate 
life for the language implementer, particularly in the area of interop.

>
> Chas did a survey in 2012, which gave very negative results for 
> clojureCLR, with 70% people having no motivation to even play with it, and 
> almost no production use.
>
>
For me, the more interesting question is:
 

> How can ClojureCLR be protected from dwindling?
>


1.  Send more fish.  :)
2.  Contribute.

We can't do much about the culture in the .Net world that impedes adoption 
of these languages , as discussed by other respondents.

The biggest impediment seems to be tooling. Progress is being made.  This 
year has seen a noticeable increase in the number of contributors. 
ClojureCLR is now also on Mono, more libs have been ported, everything is 
being made available on nuget, we have a good start in the leiningen space 
with lein-clr and nleiningen (both mentioned in a recent thread here), and 
there have been some updates on the Visual Studio plugin.

We just need more.

ClojureCLR will have an official 1.5 release any day now (it's already 
caught up to 1.5.1 on the master branch, I just haven't tagged an official 
release yet).
I'd like to see the work on lein-clr (which depends on ClojureJVM) moved 
into nleiningen (native ClojureCLR) and nlein extended to be more 
comprehensive.
The nrepl port needs to be completed so it can be incorporated into nlein, 
the VS plugin, maybe emacs.
And the the VS plugin needs continued refinement.

I am not surprised by the low numbers for ClojureCLR on the Clojure survey. 
 
I am pleased by the increase of interest and participation that I have been 
seeing.

And I'm really glad we didn't call it IronClojure. :)

-David

-- 
-- 
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/groups/opt_out.


Reply via email to