The wick blog¶
- Wick 0.3: bits you can build with — 6 October 2026
Design notes, release posts, and evidence for language decisions — the same role the Go blog plays for Go: not marketing fluff, but a durable public record of why the language looks the way it does.
wick grows only when a real game pays for a feature. The posts below are that history.
Posts¶
| Date | Title |
|---|---|
| 2026-07-14 | wick 0.2 — Release notes |
| 2026-07-14 | Admitting records |
| 2026-07-14 | Store safety is a language property |
| 2026-07-14 | How we test a tiny language |
| 2026-07-14 | Why optionals (a real crash) |
| 2026-07-14 | Welcome to the wick blog |
Also read¶
- Language overview
- Feature ledger / limits
- Engine CHANGELOG
- Engine WICK.md (in-repo source of truth)
How to propose a language change¶
- Show code that hurts in a shipped or in-progress lantern game.
- Show that a static workaround (bake offline, parallel lists, etc.) is no longer clean.
- Propose the smallest surface that removes the pain — not “feature parity with X.”
- If admitted, land language + tests + docs + this blog in one change.
That is the whole process. There is no roadmap committee.