Live data from Hacker News

Common Lisp Koans

github.com

21–24 of 24 posts

Re: Common Lisp Koans

#21
post #15
post #13

Earlier quoted context omitted.

> btw, your question assumes that Common Lisp is not evolving. This is not correct at all. Which improvements Clojure evolving consists of? Traction for one. > Transducers? Cl got them too Pointing to some random libs that implement the same concept doesn't mean it's part of a languages culture/ecosystem/common practice as transducers are to closure. E.g. I could say "Rails? Well, language X has a rails like framewor…

They should not be a part of language, what for? Everything else you mentioned is about community only, and doesn't apply directly to the language. E.g. if you have a good language without a community, community can eventually grow, but you can use the language anyway. If you have a bad language with great community - it doesn't reduce your suffering from the language itself.

>E.g. if you have a good language without a community, community can eventually grow, but you can use the language anyway. If you have a bad language with great community - it doesn't reduce your suffering from the language itself.

My experience has been the inverse.

I'd rather use a bad, or usually mediocre language WITH community, tooling, libs, books, programmers etc, than a better one where I'll be burdened by the lack of all of these.

So, in a sense, community tramps inherent language qualities.

After all that's the very basic message from Lisp and Smalltalk.

Re: Common Lisp Koans

#22
post #7

Is there any reason today to study Common Lisp instead of a more popular and evolving Lisp, like Clojure or Racket?

1. It's suitable for object-oriented programming. Common Lisp Object System is insanely powerful.

2. Depending on the implementation it can be really fast.

3. Depending on the implementation, support for typing and type inference.

+more. It's a much bigger language with a kitchen sink of features.

Re: Common Lisp Koans

#23
post #9
post #8

Earlier quoted context omitted.

Yes, they are _completely_ different languages, despite being lisps.

Thanks. Any suggestion about with which one to start? I don't believe that I'd use them for work or for many personal projects, but I've read about the advantages of learning FP. So I'd like to learn something that teaches me to think about programming in a different way and be able to apply those insights into the code I write in Java or other procedural or OO languages used at work.

Clojure is definitely a perfect fit for you then, you can even interop with your Java code.

Re: Common Lisp Koans

#24
post #22
post #7

Is there any reason today to study Common Lisp instead of a more popular and evolving Lisp, like Clojure or Racket?

1. It's suitable for object-oriented programming. Common Lisp Object System is insanely powerful. 2. Depending on the implementation it can be really fast. 3. Depending on the implementation, support for typing and type inference. +more. It's a much bigger language with a kitchen sink of features.

Note that Clojure also supports OO style with rotocols http://clojure.org/protocols and multimethods http://clojure.org/multimethodsp in fact stuff like Om https://github.com/omcljs/om/wiki/Quick-Start-(om.next) is fairly object oriented in nature.

Clojure is also very fast thanks to running on the JVM and it supports type hinting. There's also core.typed for static typing support.

Post reply on HN