Ask Douglas Panel
summary
Explains practical JSON choices: use put comments in data (comment: or comment-field:) or run through JSLint to strip them for configs; JSON is intentionally versionless so it stays unchanged. Describes new personal formats Misti (network/interprocess) and Mil (binary bytecode with Kim strings) for blobs and compact numbers. Argues JSLint-enforced JavaScript subset reduces bugs, favors actor model over threads, criticizes heavy frameworks for slowing the web, and weighs TypeScript’s benefits and costs.
AI-written summary · about
chapters (20)
- 0:00JSON comments frustration
- 1:29AI impact on junior engineers
- 2:56AI existential risks
- 4:19JSON future in AI era
- 7:09DOC bubble lessons learned
- 9:42JavaScript subset philosophy
- 13:50New language for modern web
- 14:54JavaScript frameworks debate
- 20:23TypeScript value and pitfalls
- 21:48JavaScript single-threaded benefits
- 24:23Text editor preferences
- 25:07Actor model for web development
- 26:55Node.js and server-side JavaScript
- 28:00Actor model in state management
- 30:10Future with actor model adoption
- 31:57JSON efficiency improvements
- 34:11Regrets in software design
- 35:14Decentralized systems incentives
- 37:45Open source sustainability
- 39:13Tabs vs spaces
