- High level overview https://yogthos.github.io/ClojureDistilled.html
- An Animated Introduction to Clojure https://markm208.github.io/cljbook/
- Interactive tutorial in a browser https://tryclojure.org/
- Interactive exercises http://clojurescriptkoans.com/
- Clerk notebooks with introductory examples https://github.clerk.garden/anthonygalea/notes-on-clojure
- More interactive exercises https://4clojure.oxal.org/
- Lambda Island tutorials https://lambdaisland.com/
- Functional Programming with Clojure resources https://practicalli.github.io/
If you hate git submodule
, then you may want to give git subtree
a try.
When you want to use a subtree, you add the subtree to an existing repository where the subtree is a reference to another repository url and branch/tag. This add
command adds all the code and files into the main repository locally; it's not just a reference to a remote repo.
When you stage and commit files for the main repo, it will add all of the remote files in the same operation. The subtree checkout will pull all the files in one pass, so there is no need to try and connect to another repo to get the portion of subtree files, because they were already included in the main repo.
Let's say you already have a git repository with at least one commit. You can add another repository into this respository like this:
{:paths ["." "src" "test"] | |
:deps {expound {:mvn/version "0.8.4"} | |
clansi {:mvn/version "1.0.0"} | |
cider/cider-nrepl {:mvn/version "0.24.0"} | |
refactor-nrepl {:mvn/version "2.5.0"} | |
com.bhauman/rebel-readline {:mvn/version "0.1.4"}}} |
; A REPL-based, annotated Seesaw tutorial | |
; Please visit https://github.com/daveray/seesaw for more info | |
; | |
; This is a very basic intro to Seesaw, a Clojure UI toolkit. It covers | |
; Seesaw's basic features and philosophy, but only scratches the surface | |
; of what's available. It only assumes knowledge of Clojure. No Swing or | |
; Java experience is needed. | |
; | |
; This material was first presented in a talk at @CraftsmanGuild in | |
; Ann Arbor, MI. |
A list of commonly asked questions, design decisions, reasons why Clojure 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 readibility, but never changed a sentence) from mailing lists, articles, chats.
How to use:
- The link in the table of content jumps at the copy of the answer on this page.
- The link on the answer itself points back at the original post.
{:deps {org.clojure/clojure {:mvn/version "1.10.0"} | |
com.taoensso/nippy {:mvn/version "2.14.0"} | |
org.apache.commons/commons-compress {:mvn/version "1.18"}}} |
Or, ramblings and complaints about the general state of programming and other possibly related grievances.
There are 3 primary ways to pass data into functions: move, copy, or borrow (aka a reference). Since mutability is inherently intertwined with data passing (this function can borrow my data, but only if they promise not to mess with it), we end up with 6 distinct combinations.
Every language has its own level of support and take on these semantics:
;;;; pretty-literals.lisp - pretty hash table & vector literal syntax | |
;;;; inspired by and uses code from http://frank.kank.net/essays/hash.html | |
(in-package #:pretty-literals) | |
;; vector literal syntax using brackets | |
(set-macro-character #\[ | |
(lambda (str char) | |
(declare (ignore char)) | |
(let ((*readtable* (copy-readtable *readtable* nil)) |
{:paths ["."] | |
:deps {clansi/clansi {:mvn/version "1.0.0"}}} |