Programming Power Paradox
summary
Claims that compiler vs application tooling limits automation and that multi-phase development solves it lead to a concrete proof‑of‑concept: a pure, typed DSL called Paradox domain specification language plus a Paradox Node generator. It generates TypeScript UI and a working CRUD web app (Node, Vite, in‑memory store), enforces validations, creates role‑based permissions, and supports file‑based overrides for custom logic. Language server and Nix flake are used, IO is forbidden in the DSL, and SQL migration generation is planned.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:28Programming power paradox
- 3:15Application generation goal
- 8:08Automation limitations
- 10:18Compilers vs applications
- 12:04Paradox as solution
- 14:53Live coding Paradox
- 20:16Extending applications
- 29:11Multi-phase development
- 37:04Q&A
related talks
32mTour of language landscape
28m"Making a Programming Language for 3D Design"
25m"Compiler-Driven Development: Making Rust Work for You"
36mThe language that isn't
01h 01mThree Unlikely Successful Features of D
39mCodegen your problems away - device-driver toolkit
40mTBA: Developer experience stuff?
36mWeb development with Rust, is it ready? Is it even useful?