LFE: A Real Lisp in the Erlang Ecosystem
summary
LFE claims to be a working Lisp that runs on the BEAM/OTP stack, not an emulation: it uses the VM’s immutable data, pattern matching, binaries for protocol parsing, modules/functions as BEAM requires, and macros (unhygenic, no true gensym). Implementations target Erlang 15–19, interoperate with Elixir and Erlang libraries, and already ship in production; examples include a phone-control demo that makes calls ring using message-passing and millions of lightweight processes for concurrency.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 0:25Goals for LFE
- 1:13Background
- 2:08Not out to implement a functional language
- 2:54What was the problem
- 4:57The Erlang Ecosystem
- 8:49What is the Beam
- 9:57Properties of the Beam
- 12:02Immutable Data
- 15:37Lisp Properties
- 16:25Lisp Code
- 17:24Iconic
- 21:26Atoms Symbols
- 23:38Binarys
- 26:02Modules
- 29:48Module Attributes
- 31:07Symbol Properties
- 32:41LFE Lisp
- 34:58Pattern Matching
- 36:24Expansion
- 37:29Macros
- 39:38Macro Calls
- 41:03Defining Function Types
- 42:25Why LFE
- 42:49Questions
