pull down to refresh

A list of commonly asked questions, design decisions, reasons why Clojure[1] is the way it is as they were answered directly by Rich (even when from many years ago, those answers are pretty much valid today!). Feel free to point friends and colleagues here next time they ask (again). Answers are pasted verbatim (I've made small adjustments for readability, but never changed a sentence) from mailing lists, articles, chats.

Table of ContentTable of Content

FP vs OOPFP vs OOP

Clojure DesignClojure Design

Clojure FeaturesClojure Features

Learning, Process and CommunityLearning, Process and Community

  1. Clojure is a dynamic and functional dialect of the programming language Lisp on the Java platform. Like most other Lisps, Clojure's syntax is built on S-expressions that are first parsed into data structures by a Lisp reader before being compiled. Clojure's reader supports literal syntax for maps, sets, and vectors along with lists, and these are compiled to the mentioned structures directly. Clojure treats code as data and has a Lisp macro system.