The language was started in 2007. Between then and now, the language has gained tons of recognition and a massive and extremely fast growing community. The speed at which the community has gone together and the language has become production ready is well due to the fact that Clojure can leverage any existing Java library and Java codebases. This cut out the need for libraries that most languages suffer from in the beginning.
Clojure is well on it's way to becoming a household (a coder's house, obviously) name.
Editors and Build tools
Clojure people use a whole string of different editors, mostly depending on their background, be it Java, Common Lisp, or C.
There is a set of guides to getting setup with Clojure and various tools and editors on the Confluence wiki: http://dev.clojure.o...Getting+Started
Common editors include Emacs, Vim, Eclipse, IntelliJ IDEA, and Enclojure.
While the IDE support is okay and getting better, most Clojurists like to use Emacs. Emacs is arguably the most powerful editor in existence. It's far more than just an editor, and it itself is mostly written in a custom dialect of Lisp, called elisp, which is a huge plus for Lispers, because you can use elisp to configure Emacs to do anything.
While Emac is the most popular editor, a lot of people still use Vim for Clojure. And why shouldn't they? It too is an excellent editor and has external support for Clojure via VimClojure. The above link has a page about that. The only thing I'd like to add is that you should probably use the bitbucket repository for the most up-to-date support.
As far as IDE support goes, at the time of this edit, it appears that Counterclockwise and La Clojure are the most heavily developed, in that order. IntelliJ IDEA is free now, so La Clojure is a viable option for everybody. Counterclockwise is a very viable option, and is probably the most heavy developed.
Since Clojure is on the JVM, pretty much all Java build tools work for Clojure, including Maven and Ant. There are even some build tools built specifically for Clojure with simplicity in mind for people who are too afraid of Maven (like pretty much everybody, including myself).
Common build tools are cake and leiningen. The first thing you should do when you get started with Clojure is install cake or leiningen. Don't try to 'install' Clojure. Just use cake or leiningen to get an REPL and manage your project, because that's the closest you'll get to 'installing' Clojure like you would Python or Java. All Clojure is is a jar file. Instructions for installing either of these build tools are on the dev.clojure.org link I linked above.
Leiningen is the most popular build tool and has been around for a while. Cake adds some capabilities and I use it personally, partially because my company develops it and partially because the rest of our projects depend on special features it provides. Both are actively developed and they both have the same basic features that you need, so I (nor anybody else) cares which you choose. Just choose one.
This is the fun stuff. You're all set up and ready to fire off some Clojure code, but you have to learn the language first!
First off, is the wonderful and free tutorial that lots of people start out with: Clojure - Functional Programming for the JVM. This is a good (outdated) tutorial on Clojure that might be helpful for getting you going before you're ready to buy a book.
Beyond that, there are several books published and even more in the making. There is Programming Clojure, which is already published. It's quite a bit outdated though, so I don't recommend it. There is a 2nd edition coming out soon.
A more up-to-date book is Practical Clojure which essentially serves the same purpose as Programming Clojure does, but for the newer versions of Clojure.
The most important book of them all is: Joy of Clojure, which is the book on Clojure.
Other books are in the works including Chas Emerick's Clojure Programming and my own book. The electronic version of my book will be free once it is complete. I'll be sure to highly publicize it here on DiC so that you can all get in on it.
The Clojure community is extremely active and newbie friendly. By far, the quickest and most one-on-one place to get help with anything Clojure is the #clojure IRC channel on the popular Freenode IRC network. Well over 300 people frequent that channel, and the most important people people in the community hang out there as well, including the core Clojure development team.
A less direct, but equally effective means of getting help is the Clojure maling list via Google Groups.
Those are the primary community-centered ways of getting help. There is also HERE! and places like stackoverflow.com. Admittedly, there aren't tons of Clojure programmers on this site, but there are a few, and we will try to help you to the best of our abilities and as fast as possible right here on DiC, so don't be afraid to ask questions.
Are you afraid of parens? Don't understand why Lisp has them? Read this: http://www.defmacro....lings/lisp.html
Want to try Clojure right now without installing it? Check out my TryClojure site: http://try-clojure.org, it's an online REPL written in Clojure.
Clojure has it's own reddit.
Are We There Yet: A presentation by Rich Hickey, not really related to Clojure, but is important in general.
Persistent Data Structures and Managed References: A presentation by Rich Hickey
There is a huge amount of information about Clojure right on the Clojure website. Here are a few links that should help you out if you're wondering why I lubs me some Clojure:
Clojure Rationale, this is a very important page to read, and will give you some inklings into why Clojure is designed the way it is.
Clojure Feature Page, a list of a few key features that make Clojure awesome.
If you have anything to add, post below.
This post has been edited by Raynes: 01 October 2011 - 08:22 AM
Reason for edit:: Updates