Re:Thinking in Clojure for Java Programmers
by dirtyvagabond on Thursday December 16, 2010 @05:47PM
(#2014178)
Thanks swannodette, very kind of you! Yes, it's been cool to layer Clojure on top of legacy Java and see what happens. Some want to sell Clojure as "a better Java than Java"... I think that may be a little misguided. But, there are certain situations where it rings true... at least IMHO
Re:Thinking in Clojure for Java Programmers
by swannodette on Thursday December 16, 2010 @06:01PM
(#2014243)
I don't think Clojure's goal is to be "better Java". Rather, that for whatever task you might consider Java, writing that task in Clojure should be:
* easier to write
* perform just as well
* be concurrency safe
Clojure isn't there yet, but it's well on its way I think.
Re:Thinking in Clojure for Java Programmers
by jshen on Thursday December 16, 2010 @07:50PM
(#2014601)
it's easier to have unsafe concurrency in clojure. It's certainly easier to get it right by default than in java, but it's still very easy to introduce a race condition or some such.
Re:Thinking in Clojure for Java Programmers
by jshen on Friday December 17, 2010 @11:47AM
(#2016722)
Typo, I meant easy not easier
You've done an excellent job of showing Clojure's benefits to a much, much wider audience - programmers not familiar with functional programming. Also it's compelling to hear that you're successfully using Clojure to efficiently "script" larger Java codebases.
Kudos for writing such a hype-less, non-condescending, and educational tutorial for Java/imperative programmers!