Read This! | Picolisp | Picolisp Machine | Pil Sources | Pil Tutorials | Picolisp By Example | Linux | BASH | C-Programmming | Javascipt | Python | Scheme | Operating Systems | AssemblyLanguage | Computer Security | Firewalls | Exploitation | Social Engineering | Metasploit | Emacs | vim | Pharo Smalltalk | Databases | Networking | Machine Learning | Git | Machine Learning | Algorithms | Open Data Science |

Picolisp Tutorials

Here is the truth about learning PicoLisp: the language is small enough that tutorials can take you from zero to a working app without a 900-page book. The hard part is not syntax – it is trusting that lists, symbols and a handful of forms really are enough.

What it is, in plain words

This page is the hub for PicoLisp tutorials on this site: short, concrete paths into the language, the database and the application style Alexander Burger designed. Official docs at software-lab.de remain the source of truth; these notes are how I keep the paths I actually walked.

Why it matters

PicoLisp rewards apprenticeship. A weekend with quote, fill and a tiny DB-backed form teaches more about interactive systems than a month of framework tutorials elsewhere. If Vikix is a Linux you understand, PicoLisp is a language you can hold in your head.

An everyday analogy: a workshop tour

The tutorials are stations on a workshop tour: first how to hold the tools (quote), then a small project (the health app), then you start inventing. Skip the tour and the tools look like clutter. Take it, and the clutter becomes a kit.

A hands-on path

1. Install PicoLisp (sudo xbps-install -S picolisp on Void) and run pil +.
2. Work through quote – why quoting exists and how evaluation walks lists.
3. Read PicoLisp by Example and retype the examples; don’t just glance.
4. Skim Pil Numbers, Pil I/O and Pil Box when those topics appear.
5. Build or study The Health Application – entities, forms, persistence.
6. Keep Pil Sources and Pil Machine nearby when you wonder how deep the rabbit hole goes.

(de square (N) (* N N))
(mapcar square (range 1 5))   # (1 4 9 16 25)
(load "@lib/http.l" "@lib/xhtml.l" "@lib/form.l")

When something surprises you, (doc 'map) and the REPL are the tutors.

Tutorial index

• quote – evaluation and quoting
• The Health Application – end-to-end app
• PicoLisp by Example
• Pil Examples Examined
• Pil Numbers · Pil I/O · Pil Box
• PicoLisp DB · Pil Chat · Pil Life

Common misconceptions

• “I need a big framework first.” You need pil + and curiosity.
• “Tutorials replace the docs.” They don’t. They sequence them.
• “PicoLisp is only for Retro fans.” It ships production apps today.
• “I must memorise every function.” You must learn how to ask the image (doc, show, source).

How I take notes while learning

Keep a scratch.l open next to the tutorial. After every example, change one thing – a name, a boundary, a wrong input – and see what the REPL says. Paste the survivors into your own file. Tutorials explain; your scratch file remembers.

When an official demo app exists (health, chat), run it before reading the source. Predicting what a click does, then confirming, wires the concepts faster than reading alone.

Connections

• PicoLisp, PicoLisp Machine, Pil Sources.

• Databases, Lambda Calculus.

• quote

• Here

• The Health Application