Clojure

Clojure (/ˈkloʊʒər/, like closure)[15][16] is a modern, dynamic, and functional dialect of the Lisp programming language on the Java platform.[17][18] Like other Lisp dialects, Clojure treats code as data and has a Lisp macro system.[19] The current development process is community-driven,[20] overseen by Rich Hickey as its benevolent dictator for life (BDFL).[21]

Clojure
Paradigmmulti-paradigm:
FamilyLisp
Designed byRich Hickey
First appeared2007 (2007)
Stable release
1.10.1[8] / 6 June 2019 (2019-06-06)
Preview release
1.10.2-alpha1 / 5 March 2020 (2020-03-05)
Typing discipline
  • dynamic
  • strong
Platform
LicenseEclipse Public License
Filename extensions
  • .clj
  • .cljs
  • .cljc
  • .edn
Websiteclojure.org
Influenced by
Influenced

Clojure advocates immutability and immutable data structures and encourages programmers to be explicit about managing identity and its states.[22] This focus on programming with immutable values and explicit progression-of-time constructs is intended to facilitate developing more robust, especially concurrent, programs that are simple and fast.[23][24][15] While its type system is entirely dynamic, recent efforts have also sought the implementation of gradual typing.[25]
Commercial support for Clojure is provided by Cognitect.[26] Clojure conferences are organized every year across the globe, the most famous of them being Clojure/conj.[27]

History and development process
Rich Hickey, creator of Clojure

Rich Hickey is the creator of the Clojure language.[17] Before Clojure, he developed dotLisp, a similar project based on the .NET platform,[28] and three earlier attempts to provide interoperability between Lisp and Java: a Java foreign language interface for Common Lisp (jfli),[29] A Foreign Object Interface for Lisp (FOIL),[30] and a Lisp-friendly interface to Java Servlets (Lisplets).[31]

Hickey spent about 2½ years working on Clojure before releasing it publicly, much of that time working exclusively on Clojure with no outside funding. At the end of this time, Hickey sent an email announcing the language to some friends in the Common Lisp community.

The development process is community-driven[20] and is managed at the Clojure JIRA project page.[32] General development discussion occurs at the Clojure Google Group.[33] Anyone can submit issues and ideas at ask.clojure.org[34], but to contribute patches, one must sign the Clojure Contributor agreement.[35] JIRA issues are processed by a team of screeners and finally Rich Hickey approves the changes.[36]

Clojure's name, according to Hickey, is a pun on the programming concept "closure" incorporating the letters C, L, and J for C#, Lisp, and Java respectively—three languages which had a major influence on Clojure's design.[37]

Design philosophy

Rich Hickey developed Clojure because he wanted a modern Lisp for functional programming, symbiotic with the established Java platform, and designed for concurrency.[23][24][38][15]

Clojure's approach to state is characterized by the concept of identities,[22] which are represented as a series of immutable states over time. Since states are immutable values, any number of workers can operate on them in parallel, and concurrency becomes a question of managing changes from one state to another. For this purpose, Clojure provides several mutable reference types, each having well-defined semantics for the transition between states.[22]

Language overview
Version Release date Major features/improvements
October 16, 2007[39] Initial public release
1.0 May 4, 2009[40] First stable release
1.1 December 31, 2009[41] Futures
1.2 August 19, 2010[42] Protocols
1.3 September 23, 2011[43] Enhanced primitive support
1.4 April 15, 2012[44] Reader literals
1.5 March 1, 2013[45] Reducers
1.5.1 March 10, 2013[46] Fixing a memory leak
1.6 March 25, 2014[47] Java API, improved hashing algorithms
1.7 June 30, 2015[48] Transducers, reader conditionals
1.8 January 19, 2016[49] Additional string functions, direct linking, socket server
1.9 December 8, 2017[50] Integration with spec, command-line tools
1.10 December 17, 2018[51] Improved error reporting, Java compatibility
Current stable version: 1.10.1 June 6, 2019[8] Working around a Java performance regression and improving error reporting from clojure.main
Legend:
Old version
Older version, still maintained
Latest version
Latest preview version
Future release

Clojure runs on the Java platform and as a result, integrates with Java and fully supports calling Java code from Clojure,[52][15] and Clojure code can be called from Java also.[53] The community uses Leiningen for project automation, providing support for Maven integration. Leiningen handles project package management and dependencies and is configured using Clojure syntax.[54]

Like most other Lisps, Clojure's syntax is built on S-expressions that are first parsed into data structures by a reader before being compiled.[55][15] Clojure's reader supports literal syntax for maps, sets and vectors in addition to lists, and these are compiled to the mentioned structures directly.[55] Clojure is a Lisp-1 and is not intended to be code-compatible with other dialects of Lisp, since it uses its own set of data structures incompatible with other Lisps.[19]

As a Lisp dialect, Clojure supports functions as first-class objects, a read–eval–print loop (REPL), and a macro system.[6] Clojure's Lisp macro system is very similar to that in Common Lisp with the exception that Clojure's version of the backquote (termed "syntax quote") qualifies symbols with their namespace. This helps prevent unintended name capture, as binding to namespace-qualified names is forbidden. It is possible to force a capturing macro expansion, but it must be done explicitly. Clojure does not allow user-defined reader macros, but the reader supports a more constrained form of syntactic extension.[56] Clojure supports multimethods[57] and for interface-like abstractions has a protocol[58] based polymorphism and data type system using records,[59] providing high-performance and dynamic polymorphism designed to avoid the expression problem.

Clojure has support for lazy sequences and encourages the principle of immutability and persistent data structures. As a functional language, emphasis is placed on recursion and higher-order functions instead of side-effect-based looping. Automatic tail call optimization is not supported as the JVM does not support it natively;[60][61][62] it is possible to do so explicitly by using the recur keyword.[63] For parallel and concurrent programming Clojure provides software transactional memory,[64] a reactive agent system,[1] and channel-based concurrent programming.[65]

Clojure 1.7 introduced reader conditionals by allowing the embedding of Clojure and ClojureScript code in the same namespace.[48][55] Transducers were added as a method for composing transformations. Transducers enable higher-order functions such as map and fold to generalize over any source of input data. While traditionally these functions operate on sequences, transducers allow them to work on channels and let the user define their own models for transduction.[66][67][68]

Platforms

The primary platform of Clojure is Java,[18][52] but other target implementations exist. The most notable of these are ClojureScript,[69] which compiles to ECMAScript 3,[70] and ClojureCLR,[71] a full port on the .NET platform, interoperable with its ecosystem. A survey of the Clojure community with 1,060 respondents conducted in 2013[72] found that 47% of respondents used both Clojure and ClojureScript when working with Clojure. In 2014 this number had increased to 55%,[73] in 2015, based on 2,445 respondents, to 66%.[74] Popular ClojureScript projects include implementations of the React library such as Reagent,[75] re-frame,[76] Rum,[77] and Om.[78][79]

Popularity

With the continued interest in functional programming, Clojure's adoption by the software developers on the Java platform has continued to increase. The language has also been either favored or recommended by renowned software development veterans such as Brian Goetz,[80][81][82] Eric Evans,[83][84] James Gosling,[85] Paul Graham,[86] and Robert C. Martin (colloquially known as "Uncle Bob").[87][88][89][90]

In the "JVM Ecosystem Report 2018" (which was claimed to be "the largest survey ever of Java developers"), prepared in collaboration by Snyk and Java Magazine, Clojure was ranked the 2nd most used programming language (behind Java) for "main applications".[91]

Clojure is used in industry by firms[92] such as Apple,[93][94] Atlassian,[95] Funding Circle,[96] Netflix,[97] Puppet,[98] and Walmart[99] as well as government agencies such as NASA.[100] It has also been used for creative computing, including visual art, music, games, and poetry.[101]

ThoughtWorks, while assessing functional programming languages for their Technology Radar,[102] expressed their favor toward Clojure as "a simple, elegant implementation of Lisp on the JVM" in 2010 and promoted its status to "ADOPT" in 2012.[103]

A growing number of unofficial and experimental implementations for other platforms testify to the popularity of the language:

  • CljPerl,[104] Clojure atop Perl
  • Clojerl,[105] Clojure on BEAM, the Erlang virtual machine
  • clojure-py,[106] Clojure in pure Python
  • Ferret,[107] compiles to self-contained C++11 that can run on microcontrollers
  • Joker,[108] an interpreter and linter written in Go
  • Las3r,[109] a subset of Clojure that runs on the ActionScript Virtual Machine (the Adobe Flash Player platform)
  • Pixie,[110] Clojure-inspired Lisp dialect written in RPython
  • Rouge,[111] Clojure atop YARV in Ruby

Tools

Tooling for Clojure development has seen significant improvement over the years. The following is a list of the most popular IDEs/editors with their plug-ins that combined provide excellent support for Clojure development:[112]

In addition to the tools provided by the community, the official Clojure CLI tools[123] have also become available on GNU/Linux, macOS, and Windows since Clojure 1.9.[124]

Features by example

The following examples can be run in a Clojure REPL such as one started with the Clojure CLI tools[123] or an online REPL such as one available on REPL.it.[125]

Simplicity

Because of the strong emphasis on simplicity, typical Clojure programs consist of mostly functions and simple data structures (i.e., lists, vectors, maps, and sets):

;; A typical entry point of a Clojure program:
;;   `-main` function
(defn -main ; name
  [& args] ; (variable) parameters
  (println "Hello, World!")) ; body

Programming at REPL

Like other Lisps, one of the iconic features of Clojure is interactive programming at the REPL.[126] Note that, in the following examples, ;; starts a line comment and ;; => indicates output:

;; define a var
(def a 42)
;; => #'user/a

;; call a function named `+`
(+ a 8)
;; => 50

;; call a function named `even?`
(even? a)
;; => true

;; define a function that returns the remainder of `n` when divided by 10
(defn foo [n] (rem n 10))
;; => #'user/foo

;; call the function
(foo a)
;; => 2

;; print the docstring of `rem`
(doc rem)
;; =>
-------------------------
clojure.core/rem
([num div])
 remainder of dividing numerator by denominator.

;; print the source of `rem`
(source rem)
;; =>
(defn rem
  "remainder of dividing numerator by denominator."
  {:added "1.0"
   :static true
   :inline (fn [x y] `(. clojure.lang.Numbers (remainder ~x ~y)))}
  [num div]
    (. clojure.lang.Numbers (remainder num div)))

Names at runtime

Unlike other runtime environments where names get compiled away, Clojure's runtime environment is easily introspectable using normal Clojure data structures:

;; define a var
(def a 42)
;; => #'user/a

;; get a map of all public vars interned in the `user` namespace
(ns-publics 'user)
;; => {a #'user/a}

;; reference the var via `#'` (reader macro) and
;; its associated, namespace-qualified symbol `user/a`
#'user/a
;; => #'user/a

;; de-reference (get the value of) the var
(deref #'user/a)
;; => 42

;; define a function (with a docstring) that
;; returns the remainder of `n` when divided by 10
(defn foo "returns `(rem n 10)`" [n] (rem n 10))
;; => #'user/foo

;; get the metadata of the var `#'user/foo`
(meta #'user/foo)
;; =>
{:arglists ([n]),
 :doc "returns `(rem n 10)`",
 :line 1,
 :column 1,
 :file "user.clj",
 :name foo,
 :ns #namespace[user]}

Code as data (homoiconicity)

Similar to other Lisps, Clojure is homoiconic (also known as code as data). In the example below, we can see how easy it is to write code that modifies code itself:

;; call a function (code)
(+ 1 1)
;; => 2

;; quote the function call
;; (turning code into data, which is a list of symbols)
(quote (+ 1 1))
;; => (+ 1 1)

;; get the first element on the list
;; (operating on code as data)
(first (quote (+ 1 1)))
;; => +

;; get the last element on the list
;; (operating on code as data)
(last (quote (+ 1 1)))
;; => 1

;; get a new list by replacing the symbols on the original list
;; (manipulating code as data)
(map (fn [form]
       (case form
         1 'one
         + 'plus))
     (quote (+ 1 1)))
;; => (plus one one)

Expressive operators for data transformation

The threading macros (->, ->>, and friends) can syntactically express the abstraction of piping a collection of data through a series of transformations:

(->> (range 10)
     (map inc)
     (filter even?))
;; => (2 4 6 8 10)

This can also be achieved more efficiently using transducers:

(sequence (comp (map inc)
                (filter even?))
          (range 10))
;; => (2 4 6 8 10)

Thread-safe management of identity and state

A thread-safe generator of unique serial numbers (though, like many other Lisp dialects, Clojure has a built-in gensym function that it uses internally):

(def i (atom 0))

(defn generate-unique-id
  "Returns a distinct numeric ID for each call."
  []
  (swap! i inc))

Macros

An anonymous subclass of java.io.Writer that doesn't write to anything, and a macro using it to silence all prints within it:

(def bit-bucket-writer
  (proxy [java.io.Writer] []
    (write [buf] nil)
    (close []    nil)
    (flush []    nil)))

(defmacro noprint
  "Evaluates the given `forms` with all printing to `*out*` silenced."
  [& forms]
  `(binding [*out* bit-bucket-writer]
     ~@forms))

(noprint
  (println "Hello, nobody!"))
;; => nil

Language interoperability with Java

Clojure was created from the ground up to embrace its host platforms as one of its design goals and thus provides excellent language interoperability with Java:

;; call an instance method
(.toUpperCase "apple")
;; => "APPLE"

;; call a static method
(System/getProperty "java.vm.version")
;; => "12+33"

;; create an instance of `java.util.HashMap` and
;; add some entries
(doto (java.util.HashMap.)
  (.put "apple" 1)
  (.put "banana" 2))
;; => {"banana" 2, "apple" 1}

;; create an instance of `java.util.ArrayList` and
;; increment its elements with `clojure.core/map`
(def al (doto (java.util.ArrayList.)
          (.add 1)
          (.add 2)
          (.add 3)))

(map inc al)
;; => (2 3 4)

;; show a message dialog using Java Swing
(javax.swing.JOptionPane/showMessageDialog
  nil
  "Hello, World!")
;; => nil

Software transactional memory

10 threads manipulating one shared data structure, which consists of 100 vectors each one containing 10 (initially sequential) unique numbers. Each thread then repeatedly selects two random positions in two random vectors and swaps them. All changes to the vectors occur in transactions by making use of Clojure's software transactional memory system:

(defn run
  [nvecs nitems nthreads niters]
  (let [vec-refs
        (->> (* nvecs nitems)
             (range)
             (into [] (comp (partition-all nitems)
                            (map vec)
                            (map ref))))

        swap
        #(let [v1 (rand-int nvecs)
               v2 (rand-int nvecs)
               i1 (rand-int nitems)
               i2 (rand-int nitems)]
          (dosync
            (let [tmp (nth @(vec-refs v1) i1)]
              (alter (vec-refs v1) assoc i1 (nth @(vec-refs v2) i2))
              (alter (vec-refs v2) assoc i2 tmp))))

        report
        #(->> vec-refs
              (into [] (comp (map deref)
                             (map (fn [v] (prn v) v))
                             cat
                             (distinct)))
              (count)
              (println "Distinct:"))]

    (report)

    (->> #(dotimes [_ niters] (swap))
         (repeat nthreads)
         (apply pcalls)
         (dorun))

    (report)))

(run 100 10 10 100000)
;; =>
[0 1 2 3 4 5 6 7 8 9]
[10 11 12 13 14 15 16 17 18 19]
  ...
[990 991 992 993 994 995 996 997 998 999]
Distinct: 1000

[382 318 466 963 619 22 21 273 45 596]
[808 639 804 471 394 904 952 75 289 778]
  ...
[484 216 622 139 651 592 379 228 242 355]
Distinct: 1000
nil
gollark: SC is actually quite busy.
gollark: Seriously? I need captchas for every post on the new forum? And they get invalidated if I leave them too long?
gollark: DDOS the hack matrix.
gollark: Ah, yes, the joys of PHPhorrendousness.
gollark: Still, though, why *does* it?

See also

References
  1. "Agents and Asynchronous Actions". Clojure.org. Retrieved 2019-07-07.
  2. "Concurrent Programming". Clojure.org. Retrieved 2019-07-07.
  3. Hickey, Rich; contributors. "core.async". GitHub.com. Retrieved 2019-07-07.
  4. "Functional Programming". Clojure.org. Retrieved 2019-07-07.
  5. Nolen, David; Hickey, Rich; contributors. "core.logic". GitHub.com. Retrieved 2019-07-07.
  6. "Macros". Clojure.org. Retrieved 2019-07-07.
  7. Esterhazy, Paulus. "Threading Macros Guide". Clojure.org. Retrieved 2019-07-07.
  8. Miller, Alex (2019-06-06). "Clojure 1.10.1 release". Clojure.org.
  9. Fogus, Michael (2011). "Rich Hickey Q&A". CodeQuarterly.com. Archived from the original on 2017-01-11.
  10. Hickey, Rich. "Clojure Bookshelf". Amazon.com. Archived from the original on 2017-10-03. Retrieved 2019-07-07.
  11. Bonnaire-Sergeant, Ambrose (2012). A Practical Optional Type System for Clojure (Thesis). The University of Western Australia.
  12. "Clojure Programming" (PDF). OReilly.com. Retrieved 2013-04-30.
  13. Baldridge, Timothy. "Pixie". PixieLang.org. Retrieved 2019-07-07.
  14. Ramachandra, Ramkumar. "Rhine". GitHub.org. Retrieved 2019-07-07.
  15. Edwards, Kathryn (2009-08-10). "The A-Z of Programming Languages: Clojure". Computerworld.com.au.
  16. Hickey, Rich (2009-01-05). "meaning and pronunciation of Clojure". Google.com.
  17. Krill, Paul (2012-03-22). "Clojure inventor Hickey now aims for Android". InfoWorld.com.
  18. "Clojure". Clojure.org. Retrieved 2019-07-07.
  19. "Differences with other Lisps". Clojure.org. Retrieved 2019-07-07.
  20. "Development". Clojure.org. Retrieved 2019-07-07.
  21. Hickey, Rich (2018-11-26). "Open Source is Not About You". GitHub.com.
  22. "Values and Change: Clojure's approach to Identity and State". Clojure.org. Retrieved 2019-07-07.
  23. Hickey, Rich. "Rationale". Clojure.org. Retrieved 2019-07-07.
  24. Torre, Charles (2009-10-06). "Expert to Expert: Rich Hickey and Brian Beckman – Inside Clojure". MSDN.com.
  25. "core.typed". GitHub.com. Retrieved 2019-07-07.
  26. "Investing in A Better Way". Cognitect.com. Retrieved 2019-07-07.
  27. "Clojure/conj". Clojure-Conj.org. Retrieved 2019-07-07.
  28. Hickey, Rich (2002-10-16). "[ANN] dotLisp – a Lisp dialect for .Net". Google.com.
  29. Hickey, Rich (2013-04-15). "jfli". SourceForge.net.
  30. Hickey, Rich (2013-04-03). "foil - Foreign Object Interface for Lisp". SourceForge.net.
  31. Hickey, Rich (2013-03-07). "Lisplets". SourceForge.net.
  32. "Clojure". Atlassian.net. Retrieved 2019-07-07.
  33. "Clojure". Google.com. Retrieved 2019-07-07.
  34. "Clojure Forum". clojure.org. Retrieved 2020-03-20.
  35. "Contributor Agreement". Clojure.org. Retrieved 2019-07-07.
  36. "Workflow". Clojure.org. Retrieved 2019-07-07.
  37. Rich, Hickey (2009-01-05). "Clojure Mailing List: meaning and pronunciation of Clojure". groups.google.com. Archived from the original on 2020-01-09. Retrieved 2020-01-09.
  38. Elmendorf, Dirk (2010-04-01). "Economy Size Geek – Interview with Rich Hickey, Creator of Clojure". LinuxJournal.com.
  39. Hickey, Rich (2007-10-16). "Clojure is Two!". BlogSpot.com.
  40. Hickey, Rich (2009-05-04). "Clojure 1.0". BlogSpot.com.
  41. Hickey, Rich (2009-12-31). "Clojure 1.1 Release". BlogSpot.com.
  42. Hickey, Rich (2010-08-19). "Clojure 1.2 Release". Google.com.
  43. Redinger, Christopher (2011-09-23). "[ANN] Clojure 1.3 Released". Google.com.
  44. Dipert, Alan (2012-04-17). "[ANN] Clojure 1.4 Released". Google.com.
  45. Halloway, Stuart (2013-03-01). "ANN: Clojure 1.5". Google.com.
  46. Halloway, Stuart (2013-03-10). "Clojure 1.5.1". Google.com.
  47. Miller, Alex (2014-03-25). "[ANN] Clojure 1.6". Google.com.
  48. Miller, Alex (2015-06-30). "Clojure 1.7 is now available". Clojure.org.
  49. Miller, Alex (2016-01-19). "Clojure 1.8 is now available". Clojure.org.
  50. Miller, Alex (2017-12-08). "Clojure 1.9 is now available". Clojure.org.
  51. Miller, Alex (2018-12-17). "Clojure 1.10 release". Clojure.org.
  52. "Hosted on the JVM". Clojure.org. Retrieved 2019-07-07.
  53. "Java Interop". Clojure.org. Retrieved 2019-07-07.
  54. Hagelberg, Phil; contributors. "Leiningen". Leiningen.org. Retrieved 2019-07-07.
  55. "The Reader". Clojure.org. Retrieved 2019-07-07.
  56. Hickey, Rich. "edn". GitHub.com. Retrieved 2019-07-07.
  57. "Multimethods and Hierarchies". Clojure.org. Retrieved 2019-07-07.
  58. "Protocols". Clojure.org. Retrieved 2019-07-07.
  59. "Datatypes: deftype, defrecord and reify". Clojure.org. Retrieved 2019-07-07.
  60. Goetz, Brian (2014-11-20). "Stewardship: the Sobering Parts". YouTube.com.
  61. Rose, John (2007-07-12). "tail calls in the VM". Oracle.com.
  62. Rose, John (2009-02-11). "Some languages need to be able to perform tail calls". Java.net.
  63. "Special Forms". Clojure.org. Retrieved 2019-07-07.
  64. "Refs and Transactions". Clojure.org. Retrieved 2019-07-07.
  65. Hickey, Rich (2013-06-28). "Clojure core.async Channels". Clojure.org.
  66. Hickey, Rich (2014-09-17). "Transducers". YouTube.com.
  67. Hickey, Rich (2014-08-06). "Transducers are Coming". Cognitect.com.
  68. Hickey, Rich (2014-11-20). "Inside Transducers". YouTube.com.
  69. "ClojureScript". ClojureScript.org. Retrieved 2019-07-06.
  70. "ClojureScript – FAQ (for JavaScript developers)". ClojureScript.org. Retrieved 2018-02-04.
  71. "ClojureCLR". GitHub.com. Retrieved 2012-06-28.
  72. Emerick, Chas (2013-11-18). "Results of the 2013 State of Clojure & ClojureScript survey". CEmerick.com.
  73. "State of Clojure 2014 Survey Results". WuFoo.com. Retrieved 2015-09-17.
  74. Gehtland, Justin (2016-01-28). "State of Clojure 2015 Survey Results". Cognitect.com.
  75. "Reagent". GitHub.io. Retrieved 2019-07-06.
  76. "re-frame". GitHub.com. Retrieved 2019-07-06.
  77. Prokopov, Nikita. "Rum". GitHub.com. Retrieved 2019-07-06.
  78. Nolen, David. "Om". GitHub.com. Retrieved 2019-07-06.
  79. Coupland, Tom (2014-01-17). "Om: Enhancing Facebook's React with Immutability". InfoQ.com.
  80. Goetz, Brian (2020-05-24). "Brian Goetz' favorite non-Java JVM language (Part 1 of 3)". Twitch.tv.
  81. Goetz, Brian (2020-05-24). "Brian Goetz' favorite non-Java JVM language (Part 2 of 3)". Twitch.tv.
  82. Goetz, Brian (2020-05-24). "Brian Goetz' favorite non-Java JVM language (Part 3 of 3)". Twitch.tv.
  83. Evans, Eric (2018-08-14). "Modelling Time - Eric Evans - Domain-Driven Design Europe 2018". YouTube.com.
  84. Evans, Eric (2014-11-21). "Eric Evans on Twitter". Twitter.com.
  85. "James Gostling meetup with London Java Community". YouTube.com. 2016-10-11.
  86. Graham, Paul (2016-05-06). "Paul Graham on Twitter". Twitter.com.
  87. Martin, Robert (2019-08-22). "Why Clojure?". CleanCoder.com.
  88. Martin, Robert (2018-11-29). "Unble Bob Martin on Twitter". Twitter.com.
  89. Martin, Robert (2018-08-01). "Introduction To Functional Programming". CleanCoders.com.
  90. Martin, Robert (2017-07-11). "Pragmatic Functional Programming". CleanCoder.com.
  91. Maple, Simon; Binstock, Andrew (2018-10-17). "JVM Ecosystem Report 2018". Snyk.io.
  92. "Success Stories". Clojure.org. Retrieved 2018-10-27.
  93. Liutikov, Roman (2017-12-17). "Roman Liutikov on Twitter". Twitter.com.
  94. "Jobs at Apple". Apple.com. Retrieved 2019-07-06.
  95. Borges, Leonardo (2015-07-07). "Realtime Collaboration with Clojure". YouTube.com.
  96. Pither, Jon (2016-10-04). "Clojure in London: Funding Circle – Lending some Clojure". JUXT.pro.
  97. Williams, Alex (2014-08-03). "The New Stack Makers: Adrian Cockcroft on Sun, Netflix, Clojure, Go, Docker and More". TheNewStack.io.
  98. Price, Chris (2014-04-11). "A New Era of Application Services at Puppet Labs". Puppet.com. Retrieved 2020-08-06.
  99. Phillips, Marc (2015-07-14). "Walmart Runs Clojure at Scale". Cognitect.com.
  100. "Common-Metadata-Repository". GitHub.com. Retrieved 2019-07-06.
  101. Meier, Carin (2015-05-06). "Creative computing with Clojure". OReilly.com.
  102. "Frequently Asked Questions - Technology Radar - ThoughtWorks". ThoughtWorks.com. Retrieved 2019-02-10.
  103. "Clojure - Technology Radar - ThoughtWorks". ThoughtWorks.com. Retrieved 2019-02-10.
  104. Hu, Wei. "A Lisp on Perl". MetaCPAN.org. Retrieved 2019-07-06.
  105. Facorro, Juan. "Clojerl". GitHub.com. Retrieved 2019-07-06.
  106. Baldridge, Timothy. "clojure-py". GitHub.com. Retrieved 2019-07-06.
  107. Akkaya, Nurullah. "Ferret". Ferret-Lang.org. Retrieved 2019-07-06.
  108. Bataev, Roman. "Joker". Joker-Lang.org. Retrieved 2019-07-06.
  109. Cannon, Aemon. "Laz3r". GitHub.com. Retrieved 2019-07-06.
  110. Baldridge, Timothy. "Pixie". PixieLang.org. Retrieved 2019-07-06.
  111. Connor, Ashe. "Rouge". GitHub.com. Retrieved 2019-07-06.
  112. Miller, Alex (2019-02-04). ""State of Clojure 2019" Results". Clojure.org.
  113. Szabo, Maurício. "Chlorine: Socket REPL Client for Clojure and ClojureScript". Atom.io. Retrieved 2019-07-05.
  114. Batsov, Bozhidar; contributors. "CIDER: The Clojure Interactive Development Environment that Rocks". CIDER.mx. Retrieved 2019-07-05.
  115. Shrago, Greg. "Clojure-Kit: Clojure and ClojureScript plugin for IntelliJ-based tools". JetBrains.com. Retrieved 2019-07-05.
  116. Fleming, Colin. "Cursive: Provides full Clojure and ClojureScript language support". JetBrains.com. Retrieved 2019-07-05.
  117. Pope, Tim. "fireplace.vim: Clojure REPL Support". VIM.org. Retrieved 2019-07-05.
  118. Monroe, Dominic (2016-12-13). "Clojure and Vim: An overview – It's very possible". JUXT.pro.
  119. Masashi, Iizuka. "vim-iced: Clojure Interactive Development Environment for Vim8/Neovim". GitHub.com. Retrieved 2020-03-13.
  120. Caldwell, Oliver. "Neovim Clojure(Script) tooling over prepl". GitHub.com. Retrieved 2019-11-09.
  121. Caldwell, Oliver (2019-11-06). "Getting started with Clojure, Neovim and Conjure in minutes". oli.me.uk.
  122. Strömberg, Peter. "Calva: Clojure & ClojureScript Interactive Programming". VisualStudio.com. Retrieved 2019-07-05.
  123. Miller, Alex. "Deps and CLI Guide". Clojure.org. Retrieved 2019-07-08.
  124. Miller, Alex (2017-12-08). "Clojure 1.9". Cognitect.com.
  125. "Online Clojure REPL". REPL.it. Retrieved 2019-07-08.
  126. "Programming at the REPL: Introduction". Clojure.org. Retrieved 2018-12-04.

Further reading

Official website

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.