How does Bundler work anyway?
summary
History of Ruby packaging leads to a concrete claim: Bundler performs install‑time dependency resolution, writes an exact list in Gemfile.lock, and loads those specific versions instead of letting `require` or `gem install` pick them. It solves NP‑complete version graphs with heuristics so most Gemfiles resolve in seconds (some historically took minutes), provides bundle exec to set a correct load path at run time, and generates bundle binstubs so app commands reliably run the intended gem versions.
AI-written summary · about
chapters (19)
- 0:00how does bundler work, anyway?
- 0:35a brief (?) history of dependency management
- 2:06let's share ruby code
- 2:17Terminal: $ bundle exec foo
- 3:19dependency timeline
- 4:55run code twice?
- 5:57only absolute paths?
- 7:10load paths are
- 9:43how do setup.rb? ruby setup.rb setup ruby setup.rb config ruby setup.rb install
- 10:09Use Ruby libraries 1. Find a cool library 2. Download the library 3. Untar the library 4. Run 'ruby setup.rb all'
- 11:01no versions no uninstall
- 12:00maybe a little bit incredibly tedious
- 12:17what if you could... gem install gem uninstall gem list rails
- 16:00Welcome to the team, here's your machine. We expect setting up to take a week
- 18:36version conflicts
- 18:50activation errors
- 20:13wait... how do we resolve at install-time?
- 22:03bundle install, my old friend
- 23:23or if you're too busy, fund this work.
