By bloid
via technotales.wordpress.com
Published: Oct 11 2008 / 17:01
Clojure is a Lisp on the JVM. The J in JVM is the least interesting part of the JVM (in fact, it would probably be a good idea to rename it completely) but the JVM technology itself is amazing. You can read up about it here or here. Targeting the JVM as a platform means getting garbage collection and the other JVM performance optimizations for free. After reading about the technology, it seems silly to waste time reinventing the wheel and creating your own virtual machine / environment for your new language.
SaveShareSend
Tags: other languages
Comments
Motion Control replied ago:
No.
karmazilla replied ago:
Elaboration?
sproketboy replied ago:
LISP? Who uses that? 7 people? So Motion Control is right. Lisp on Java is NOT the the next big thing.
OtengiM replied ago:
No. Nobody likes Lisp, the average programmer Joe will not use Lisp they will use Python or PHP, Just a few folks use Lisp better let like that. There is not the next best thing, that idea is OVER.
OtengiM replied ago:
Someone in a blog was talking about Smalltalk maybe I believe more that Smalltalk is the next thing but I have to run over the JVM. And Smalltalk syntax rocks is very easy for average programmer Joe to learn it.
newton_dave replied ago:
While I'm more a fan of Lisp than Smalltalk, I agree that it's more likely that Smalltalk is more likely to gain traction, for a variety of reasons. Having been a user of both for a couple of decades I sure *hope* one or the other picks up (as Smalltalk is doing, yet again)--it's fantastic stuff.
sproketboy replied ago:
Nope. Smalltalk had its chance in the 90's and was heavily promoted by IBM. There were a couple of spectacular project failures around it mainly due to what I call the Surface Area problem. In a nutshell, this is the amount of code a developer needs to understand in a system in order to maintain a piece of code. Smalltalk tends to grow a huge surface area due to it's obsession with object purity and overuse of operator overloading. C# has this problem too - Java does not.
This probably accounts for some of the success of Java relative to C# and Smalltalk.
Voters For This Link (6)
Voters Against This Link (5)