I've been studying network analysis recently, in an attempt to
automatically infer relationships between various Clojure projects. If
a program can determine which similar libraries are good replacements
for eachother, and which libraries tend to work well together, I can
build a browseable directory of Clojure libraries. While this is
initially more difficult than building such a directory manually, I
would expect the long term maintenance costs to be lower and for the
directory to remain more up-to-date.
As an intermediate step in that goal, I collected information about
hundreds of Clojure projects, and mapped out the relationships of
projects based on who contributed to them. A pair of projects are
considered connected if they have at least two contributors in common.
I removed projects with less than two connections so that the network
would be easier to visualize.
You can see a picture of the resulting network at the top of this article.
http://ericlavigne.wordpress.com/2011/01/30/a-tour-of-the-clojure-landscape/
I noticed that, while I was familiar with a lot of the projects, those
projects tended to be clumped together into a few small parts of the
graph. With that in mind, I thought it would be useful to briefly
introduce various projects from different parts of the network (some
of which I just discovered in these last few days after seeing the
network).
--
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
