Are we there yet? Remix
summary
ClojureScript claims practical differences: an editor-connected REPL that hot-evaluates into the browser, value equality without coercion so deep comparisons and maps with complex keys work out of the box, and a runtime spec system that both instruments functions and generates concrete examples from specs. The workflow shows failing tests with explanatory errors, gradual specification reuse across data shapes, and how those runtime checks and examples solve problems that static TypeScript types alone struggle to express.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:39Closure and Closure Script
- 6:43Why Remix
- 10:24Interface
- 12:08Whats next
- 14:11Closure Script
- 17:19Equality
- 20:54Specifications
- 21:51First name last name
- 22:34Reusing specs
- 23:14Types as documentation
- 26:33Instrumentation
- 26:53Testing
- 27:28Controversial statements
related talks
29mAn adequate intro to ClojureScript
35mThrough the Looking Glass
49mClojureScript: Fun and productive web development with next level tooling
27mBuilding functional Front-ends with ClojureScript
34mClojureScript: The Essence of Alchemy
24mUsing backend languages for frontends: Why ClojureScript is an awesome idea!
01h 14mInterview and Q&A with David Nolen
56mJS.Next and CoffeeScript