Good videos, with context.
Clojure for Lisp Programmers Part 1 - Rich Hickey

Clojure for Lisp Programmers Part 1 - Rich Hickey

ClojureTV
1 HN recommenders · discussed 2017–2019
Open YouTube ↗

About this video

Rich Hickey presents an extensive introduction to Clojure at the Boston Lisp meeting, assuming prior Lisp knowledge. It covers the language's design decisions relative to other Lisps.

Why it appears in the archive

Referenced for Hickey's reasoning on design choices such as macros and not building on SBCL.

AI-generated summary and labels from the source dataset; verify important details against the video. Source & credits.

From the Hacker News discussion

tosh · 2019-07 · rec

Context: this is not only a very good introduction to Clojure and the design decisions made by Rich Hickey it also is a video that isn't very widely known. The video was uploaded to Youtube after the migration from Blip.tv but somehow got broken ( [VIDEO] ) and lived in a parallel universe in Youtube. I remember I found the video a few years ago but was unable to watch it. Last year someone re-uploaded the video to Youtube and it seems to works now. Transcript: [LINK]

Read original comment ↗
joe-user · 2017-11 · reference

> Pity he hadn't heard of Armed Bear Common Lisp ( [LINK] ), which runs on the JVM. He was certainly aware of SBCL. He had a number of reasons for not wanting to use it. [1] > I don't mind mutable state, since the real world is not functional: I hear this argument often, but the "real world" is not linked lists or hash maps or mutable or 0s and 1s either, but they are all useful representations. > real programs are all about side effects Clojure has plenty of facilities for side effects, and without having to resort to monads (though you could if you wanted). [1]: [VIDEO]

Read original comment ↗
aidenn0 · 2019-01 · reference

Hy may have changed since I last looked at it, but when I had looked at it, Hy was more of an s-expression syntax bolted onto python. Some random thoughts on why this matters: Clojure is very much not a thin s-expression layer for java; that would have been terrible (Python is more like lisp than java which is why Hy is tenable whatsoever). In particular, CL style macros with out some first-class concept of symbols are a footgun[1], but I'm sure I could find other issues. Another item that can't be ignored is that Hy selected the clojure syntax, which is going to be a turn-off for anyone coming from Lisp or Scheme. Finally, there are hundreds of thin s-expression layers on top of existing languages, and most of them are terrible; Hy has done nothing to stand out from this crowd, so most lispers will not look closely at it. 1: See [VIDEO] for Rich's discussion of how he managed this issue in Clojure.

Read original comment ↗