road map for clojure?

[julius]

Hi,

Is clojure under dev? there is no much commits in months, any plan or road map  for clojure?

thanks

[John D. Hume]

Are you looking at the right repo?

https://github.com/clojure/clojure/commits/master

--
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clo...@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+u...@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+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
http://elhumidor.blogspot.com/

[Sean Corfield]

Roadmap: http://dev.clojure.org/jira/browse/CLJ#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel

> --
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clo...@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+u...@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+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.



--

Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
World Singles, LLC. -- http://worldsingles.com/

"Perfection is the enemy of the good."
-- Gustave Flaubert, French realist novelist (1821-1880)

[Andy Fingerhut]

Also a list of features planned for Clojure 1.6, and some that were postponed to after Clojure 1.6:

    http://dev.clojure.org/display/design/Release.Next+Planning

Andy

[Mikera]

Even looking at this repo, it's not many commits. I count around 50 commits in the last 6 months.

By way of comparison, JRuby and Scala both have more than that in the last couple of weeks.

P.S. Not intended as a criticism of anybody: just an observation.

[Andy Fingerhut]

I'm not saying it puts the total number of commits up with other projects, or that it needs to, but the development of core.async has effectively been part of the core Clojure development work done in the last several months, and it has been moving along:

    https://github.com/clojure/core.async

Andy

[Michael Klishin]

2013/10/31 julius <wee...@gmail.com>

Is clojure under dev? there is no much commits in months, any plan or road map  for clojure?

I don't remember the exact quote but Clojure is developed as fast as it is designed.
It's a pretty well known fact that Clojure's primary designer prefers to analyze the problem
deeply first [1].

This is also why it is one of the most stable languages out there.

1. http://www.youtube.com/watch?v=f84n5oFoZBc
--
MK

http://github.com/michaelklishin
http://twitter.com/michaelklishin

[Baishampayan Ghose]

Please don't judge activity of a programming language ecosystem by
just looking at the frequency of commits in the main language. Clojure
the language evolves relatively slowly and every new feature is added
after a lot of careful design.

Unlike most mainstream languages many important features of Clojure
are developed as libraries, eg. core.async, core.typed, core.logic,
etc.

Clojure is a very actively used and developed [with] language with a
vibrant community. If you want to look at any superficial metric at
all, then you may look at the frequency & quality of posts made on
this list as a key indicator.

~BG

> --
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clo...@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+u...@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+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.



--

Baishampayan Ghose
b.ghose at gmail.com

[Craig]

As Alan Kay said: "Lisp isn't a language, it's a building material." So we might ask: What other properties do we builders require from this material?

[Gary Trakhman]

Seems to me clojure's went past critical mass in terms of sustainability a long time ago.

The ideas are going to be relevant until shared-memory architecture and systems made of those no longer dominate our hardware and thought processes, which is not within the foreseeable future.

Maybe 15 years from now we'll all be running erlang or NetKernel :-).

On Thu, Oct 31, 2013 at 6:39 AM, Craig <craig....@gmail.com> wrote:

As Alan Kay said: "Lisp isn't a language, it's a building material." So we might ask: What other properties do we builders require from this material?

--

[Alex Miller]

Hi Julius,

Clojure is (always) under dev. The issue and commit pipeline is bursty due to the process followed by contributors (http://dev.clojure.org/display/community/JIRA+workflow, more links here: http://dev.clojure.org/display/community/Contributing). Tickets pool in the Screened list and periodically Rich Hickey reviews and ok's them in batches. In general, Rich values quality (of patches and Clojure in general) and stability much higher than quantity of patches. Most tickets go through 2 rounds of triage (screener and Rich) and 2+ rounds of review (screener, Rich, sometimes Stu, sometimes multiple rounds) before being committed. 

The choice of which tickets move through the process into development is largely initiated by me at the moment (as I'm the only one actively triaging tickets recently). That process is unscientific but I am more likely to triage defects over enhancements, problems seen in real apps over corner cases, more votes/watches over less (report), and focus areas (error msgs, performance) over non-focus, etc. 

Clojure 1.6 is in the final stages right now with a push toward an expected release probably in December timeframe. A road map for 1.6 and things that were pushed out of 1.6 can be found at http://dev.clojure.org/display/design/Release.Next+Planning. Sometime in the next month or two that list will be updated for the next release (and possibly one beyond). 

I was hired by Cognitect to provide an active, continuous level of attention to this and other areas of Clojure development (docs, events, etc). For various reasons, I have actually been on client work 60-80% of the time but that is now ramping down so I can spend a greater percentage of my time solely on Clojure.

Happy to answer any other questions about the current state of things. 

Alex Miller

alex....@cognitect.com

[Cedric Greevey]

Who else is amused to find that gmail offers to make you an appointment in your calendar for even something as distant as "15 years from now"?

--