Saving Ruby from the Apocalypse
summary
A wild future-of-Ruby allegory presents a clear claim: Ruby is not dead but risks irrelevance because of unmaintained libraries, dwindling new gems and fewer products and jobs. Concrete remedies include blogging what works, learning ideas from other camps, reclaiming abandoned projects (examples: Richard Schneeman reviving sprockets, Justin Searles for RSpec‑Given), and actually building new libraries and products. A one‑page check of current status lives at isrubydead.com and the call to action is practical: build new gems.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:37The Ruby apocalypse story
- 7:30Identifying the problems
- 10:20Researching other communities
- 12:24Solutions for relevance
- 15:15Implementing the solutions
- 17:56The hype cycle of Ruby
- 21:44Conclusion and call to action
related talks
27mRuby in 79 AD (Open Sourcing my Role as Indiana Jones)
35mMaking it on your own and the pitfalls of gem dependencies
29mHow to Break into Reading Open Source
30mFeats of Daring with the Ruby Standard Library
31mOpen Source: Power and the Passion
37mOpen Source Maintenance
37mExtreme Makeover: Rubygems Edition
26mContributing to Rails? Start with the Gems You Already Use