Clojure could be to Concurrency-Oriented Programming what Java was to OOP

Does anyone else think so? I'm using Clojure a lot and really like it.<p>But Lisp has been around for 50 years and never hit the mainstream so it seems there perhaps is something about it that doesn't fit with most programmers?<p>Also it only offers one form of concurrnecy and while I like it there is still much speculation and research in the area. Scala for example kind of builds on the whole Java-language and offers a more recognizable language for Java-developers and more opportunities to roll your own concurrency-mechanisms, or at least that's the impression I've gotten.<p>And then we have Haskell and Erlang.

This title is horrifying!!! Java set back good OOP by about 20 years!!! We're still recovering from what Java did to the OO community.

If only we could convince someone to create Projure -- a Prolog-like language that compiles to JVM bytecodes. I'd be the first (and only?) customer.

In other words, a horrible example of?

We can't keep stepping backwards to support changing processor technologies. Concurrency should be abstracted away from the programmer, and handled on a compiler level, irrespective of your programming language.

Clojure is neat and all, but I can't see it being anything but a proving ground for some more esoteric technologies or methods. Lisp has been around too long to get mainstream acceptance and the "power vaccum" of which PG is fond of mentioning is marginal these days due to Ruby, Python, etc. Clojure has the attractiveness of running people's existing infrastructure (i.e. the JVM) but its nowhere near being alone in that regard. Its neat but don't look for it to be a world-changer.

I thought that was Erlang.