Dynamic vs Static Having a Discussion without Sounding Like a Lunatic
summary
Argues that type systems are a business decision not a purity test: compiled Clojure to FPGAs (pipin) exists and is used, Clojure and Scala run a Two Sigma compute rebuild, V8’s hidden classes show JavaScript carries implicit types for performance, PayPal reports Node sped things up and reduced bugs, GitHub runs on Ruby, and formal tools like Bluespec/Clash/Chisel and even TLA+ see production use — AWS SREs use TLA+ to verify services.
AI-written summary · about
chapters (24)
- 0:00Intro
- 1:04Who am I?
- 4:45JSON-Rich Representation
- 5:40Why is it so popular?
- 7:26JSON's Hidden Types
- 12:38There's something there
- 13:53Github
- 14:31Problem with Ruby
- 16:24What are we really talking about?
- 17:52The World's a Scary Place
- 19:29Paul Snively
- 22:09Beer Snobs
- 23:13Why are we even paid?
- 23:44The Plan
- 26:03Who is your type system for?
- 27:41Who are you talking to?
- 28:39Critical Systems
- 28:57Impact of Issues
- 30:14How do we trust our software?
- 32:41Matt's Spaceship
- 34:23David's Distributed Systems
- 35:55FPGA
- 38:51Theorems and Proofs?
- 41:39Types feel like less commitment
related talks
36mWhen to be Weird
46mThoughtful Software Engineering
54mSeeing Like a Programmer - Resiliency, Limits, And Moral Hazards In SE
01mIdan Gazit, GitHub, ETLS Vegas (29)
39mOkay your hipster tech is cute, but I run production - Clément Delafargue
39mThings that Matter
56mThings you thought you didn’t need to care about that have a big impact on your job
43mBringing Functional Programming to Work