Takes
gem and bundler CLI tools) to the same Ruby org that governs the language itself.
It's an accident of history that Ruby, its dependency tools, and its dependency hosting are managed by three separate entities. (And it hasn't gone great.)
Shots
Shorter-form
Short-form
Permalinks
This debate has been eating at me ever since the news first broke, but I've tried to keep the peace by staying out of it. Unlike most discourse about what's going on, my discomfort stems less from the issue at hand—what Ruby Central did, how they did it, and how poorly it was communicated—and more to do with how one-sided the public discussion has been. Beneath the surface of this story are the consequences of a decade-old conflict that was never fully resolved. Then and now, one side—Andre Arko and many people associated with him—has availed itself of public channels to voice their perspective, while the other—which includes a surprisingly wide swath of well-known Ruby and Rails contributors—has chosen to stay silent.
Newsletters
In case you don't subscribe to my every waking moment, some highlights of stuff I put out over the last month:
- Shared some of what I've learned about using Apple's on-device LLM API
- Suggested a new Star Wars watch order
- Opined about why I wasn't cut out for management
- Recorded two normal podcasts (v42 and v43) as well as an interview with Scott Werner
- Repeated my tireless appeal to get folks blogging again
- Gave up on Claude Code (which Anthropic has now admitted they made dumber for over a month) in favor of OpenAI Codex—specifically, this fork
- Published a command-line tool called imsg for exporting iMessage archives
- From that, I documented a how-to guide on distributing scripts via homebrew
- Did an hour-long review and buyer's guide of the aforementioned iPhone event (pre-orders go up Friday morning at 8 AM Eastern!)
Every month, I scroll through the last month of photos for one to include in this newsletter. Not many pictures this month, so here's a little surprise Becky left me that showed up in our iCloud Shared Photo Library
Merge Commits
Digest
This debate has been eating at me ever since the news first broke, but I've tried to keep the peace by staying out of it. Unlike most discourse about what's going on, my discomfort stems less from the issue at hand—what Ruby Central did, how they did it, and how poorly it was communicated—and more to do with how one-sided the public discussion has been. Beneath the surface of this story are the consequences of a decade-old conflict that was never fully resolved. Then and now, one side—Andre Arko and many people associated with him—has availed itself of public channels to voice their perspective, while the other—which includes a surprisingly wide swath of well-known Ruby and Rails contributors—has chosen to stay silent.
Breaking Change
I didn't get a good job connecting this version's release to what I was referencing, so to be clear I was referring to my heart rate as opposed to any other bodily functions. The other ones are getting up just fine, thank you. Get your head out of the gutter.
This debate has been eating at me ever since the news first broke, but I've tried to keep the peace by staying out of it. Unlike most discourse about what's going on, my discomfort stems less from the issue at hand—what Ruby Central did, how they did it, and how poorly it was communicated—and more to do with how one-sided the public discussion has been. Beneath the surface of this story are the consequences of a decade-old conflict that was never fully resolved. Then and now, one side—Andre Arko and many people associated with him—has availed itself of public channels to voice their perspective, while the other—which includes a surprisingly wide swath of well-known Ruby and Rails contributors—has chosen to stay silent.