Opening Keynote: The Journey to Zeitwerk
summary
Claims that Zeitwerk replaces the brittle Classic autoloader and ships with Rails 6 while preserving an opt‑out for upgrades; it implements file-to-constant mapping by scanning the tree, registering Module#autoload entries and decorating require, and it uses TracePoint to handle implicit namespaces. The project becomes the Zeitwerk gem integrated into Rails, proves itself on large codebases (Shopify with ~25k classes), removes hundreds of manual requires in real projects, and ships successfully.
AI-written summary · about
chapters (16)
- 0:00Keynote introduction
- 1:05Autoloading in Rails history
- 2:35Classic Auto Loader challenges
- 4:23Ruby constant lookup
- 14:00Classic Auto Loader flaws
- 17:12Ruby autoload method
- 19:45Implementing new autoloader hurdles
- 28:13TracePoint breakthrough
- 32:27Project refactoring scope
- 35:53Zeitwerk Rails integration
- 41:37Module autoload deprecation
- 46:33Zeitwerk shipped Rails 6
- 51:05Zeitwerk testing Shopify
- 55:30Zeitwerk migrations adoption
- 59:42Zeitwerk impact on Rails
- 1:00:28Autoloading future
