Re:The Axis Of Eval: Why I ignore Clojure
by rbanffy on Monday September 20, 2010 @10:58AM
(#1709033)
> We don't have decades to wait and see how a language feature "plays out"
I think the difference of perspective comes from the different nature of the work Lisp is being used for.
If your job is to create the next version of Lisp, it makes sense to watch how that new feature of Clojure plays out.
On the other hand, if your job is to deliver a nice application to users who need it, you don't really care about how that feature will look 20 years from now - you use it if it makes your problem simpler to solve.
That said, I wish application developers were less susceptible to language/library/framework fashion. I dread to support (and enhance) Java apps that rely on a stack of frameworks like the developers were playing some buzzword bingo game with the product.
I think the difference of perspective comes from the different nature of the work Lisp is being used for.
If your job is to create the next version of Lisp, it makes sense to watch how that new feature of Clojure plays out.
On the other hand, if your job is to deliver a nice application to users who need it, you don't really care about how that feature will look 20 years from now - you use it if it makes your problem simpler to solve.
That said, I wish application developers were less susceptible to language/library/framework fashion. I dread to support (and enhance) Java apps that rely on a stack of frameworks like the developers were playing some buzzword bingo game with the product.