Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Like so many things, <strong>it depends on what you want to do</strong>. </p> <p><strong>Remember, if you choose one now, it doesn't preclude you from changing later</strong>. In fact, I found it quite easy to switch from knowing a little Scheme to learning a lot of Clojure.</p> <p>If you just want to learn, and play around with a Lisp, or even build moderately complex programs, I'd say Scheme is probably a better bet. It's got a cleaner, crisper (smaller) standard library, and there are a lot of resources out that that cater to the learner (not that there aren't for CL, either).</p> <p>If you want the raw power of tons of libraries (many very well written) and the toolkit of a standard (as standard as a CL implementation gets) library that comes with a CL, then it'd be your better bet. </p> <p>Alternatively, I'd suggest <a href="http://clojure.org/" rel="noreferrer">Clojure</a>. It's a relatively new language (&lt; 5 years), but it's got a lot going for it. It's built for concurrency, with plenty of primitives that make it <em>easy</em> to write state-safe programs if you need to have state. And plenty of other perks, though again, the standard library <a href="http://richhickey.github.com/clojure/" rel="noreferrer">manages to stay small</a>.</p> <p>It's also on the JVM, so you have access to all the libraries you would if you were using Java, should you need any of them, plus the raw speed that the JVM has to offer is at your fingertips. </p> <p>However, it is a new language, with a new (but very friendly!) community. If you just want to dip your toes in the pool of Lisp, I'd say Scheme is your best bet. If you want to get things done, my preference and my love is Clojure. </p> <p><strong>EDIT</strong> Honestly, you can't go wrong with any of the three. One may be better depending on what you want to do, and I'd recommend Clojure to just about anyone. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload