51–60 of 67 posts
Python looks like a lot less typing.
And much more readable, without the parenthesis balancing dance.
LISP is the coolest language ever and maybe forever, in theory. In practice, it also works phenomenal, but just for 1%.
Just an amateur opinion although.
If I want fast performance I code in C or other low level language. Sorry Clojure community, I'm not drinking the kool aid this time.
I can only admire the persistance (free time) of someone coding in Clojure. Everytime someone says to me "I hate Objective-C syntax" I show them Clojure... If I want fast performance I code in C or other low level language. Sorry Clojure community, I'm not drinking the kool aid this time.
For me, Clojure is great because it allows you to build powerful abstractions and has some interesting concurrency constructs, while running on the JVM and making it easy to interoperate with Java code. Of course, being a Lisp, it uses Lisp syntax.
I can only admire the persistance (free time) of someone coding in Clojure. Everytime someone says to me "I hate Objective-C syntax" I show them Clojure... If I want fast performance I code in C or other low level language. Sorry Clojure community, I'm not drinking the kool aid this time.
Most of us just get stuff done using Clojure, quickly, getting concise and most importantly — correct code, even in massively multithreaded applications.
Would love to see this in Ruby
Very much agreed. Although clojure might be faster, it is so so difficult to read, and from a rubyist's POV, looks like a disaster compared to python. Maybe that's just a result of being spoiled by super clean syntax and almost human readable methods... but that's gotta count for something
This is really neat. Although, one thing that makes it easier to map this program from Python to Clojure is that the original program was written in a pretty functional style. It would be interesting to see if a more imperative sample program, or one using more object-oriented features, would map similarly.
I agree. For some things, like more mathy things that only perform one function, it seems like functional programming is the way to go. However, for HUGE programs based on data and complex interactions between and extensions of objects, it seems like a more object-oriented style would be better... all about the right tool for the job, I guess.
Coming from Ruby this approach was a bit mind-boggling at first, but even with my fairly limited Clojure exposure (or should that be expojure?) I've come to appreciate how easy pure functions are to test and to reason about.