Long journey of Ruby standard library
summary
Explains exactly why `require` sometimes raises LoadError under bundle exec and how RubyGems versus the interpreter differ, demonstrates Bundler’s use of the p-graph resolver and shows an empirical slowdown (extended require ~3.8× slower in one bigdecimal test), describes the auto‑sync and packaging work that moves libraries into default/bundled gems, lists concrete failure modes (C extensions placed in wrong directories, cross‑compilation and activation/version collisions), and lays out fixes and migration steps aimed at Ruby 3.4.
AI-written summary · about
chapters (14)
- 0:00Ruby standard library journey
- 2:14History of Ruby libraries
- 5:08RubyGems impact
- 8:48RubyGems require method
- 10:36Bundler dependency resolution
- 12:25PGraph engine
- 17:29Bundler cleanup
- 19:17Default gems explained
- 23:56Default gems benefits
- 27:09Ruby 3.3 default gems
- 29:18Ruby 3.4/3.5 plans
- 32:56C extension challenges
- 34:17Namespace improvements
- 36:47Summary
