303e8c6306
All 117 inter-node links now use [[file:node-name.org][title]] format which renders as clickable hyperlinks in both Emacs (C-c C-o) and web-based org renderers (Gitea, GitHub). Each node retains its :ID: UUID property for Emacs org-roam database features (backlinks, capturing, node-find). Prev format: [[id:uuid][title]] — Emacs only, dead text on web New format: [[file:name.org][title]] — works everywhere
19 lines
1.6 KiB
Org Mode
19 lines
1.6 KiB
Org Mode
:PROPERTIES:
|
|
:ID: 9af13fff-9725-542b-93b1-a555bc74ad72
|
|
:END:
|
|
#+title: Why Lisp Is Economically Viable Now
|
|
#+filetags: :passepartout:economics:lisp:history:C:viability:
|
|
|
|
The 1980s trade-off was: C is cheap enough for the market. Correctness is a luxury the market cannot afford. The 2020s trade-off is: C is expensive for the market. Incorrectness has become the dominant cost of software. Lisp's verification infrastructure is now the cheaper option.
|
|
|
|
Four transformations flipped the economics:
|
|
|
|
1. **Memory is free.** 40MB runtime is noise on a $20 Raspberry Pi with 8GB RAM. In 1980, DRAM was ~$5,000/MB.
|
|
2. **Transistors are free.** Modern ARM Cortex-A72 has billions of transistors. GC and type dispatch cost nothing because the transistors are there whether used or not.
|
|
3. **Complexity saturates human verification.** Systems are tens of millions of lines. Testing is necessary but insufficient — zero-day vulnerabilities prove bugs survive all testing. Formal verification is the only known path.
|
|
4. **Cost of failure exceeds cost of verification.** A single breach costs millions. Regulation mandates provable compliance. Proving correctness is cheaper than not proving it.
|
|
|
|
The verification appliance (AGPL symbolic engine + RISC-V Lisp μcode on FPGA) costs $5,000/year and replaces $500,000/year in compliance audits, breach litigation, and regulatory fines.
|
|
|
|
See also: [[file:self-driving-lisp-machine.org][Self-driving Lisp Machine]], [[file:biology-parallels.org][Biology parallels]], [[file:comparison-with-symbolics.org][Symbolics comparison]], [[file:cost-structure.org][Cost structure]], [[file:ai-industry-impact.org][AI industry impact]]
|