Richard Schneeman

@schneems.bsky.social

- Possibility space explorer 🚀 - Open source teacher and author https://howtoopensource.dev. - Ruby 3.2+ core committer - Creator of https://www.CodeTriage.com. - (he/him) Y’all means all

Flying into RubyKaigi, I thought we had months to stand up AI-assisted vulnerability scanning for rubygems.org. Turns out we were out of time. We started prototyping during the conference, scanned the most critical gems, and four hours later submitted our first advisory to Nokogiri.

Scaling Ruby's defenses with AI

On April 23rd, we submitted a vulnerability report to the Nokogiri maintainers. It was the first one our team has filed using AI-assisted scanning. The maintainers accepted the report and published...

blog.rubygems.org

At 37:30 it gets into DREAM, which is the initiative that I proposed, Driving Ruby's Evolution to AI Maturity. The problem we face is that Ruby is not showing up at the table. You go to a new API or SDK and you get JS/TS, Python, and maybe Go. A decade ago Ruby was front and center.

RubyConf 2026 is evolving and we have updates to share. We reimagined several new programs to best serve the community right now. The full program and schedule is dropping very soon. Early bird pricing ends April 30. Read the full update:

RubyConf Updates

If you haven't yet seen the statement from the Ruby Central Board, the organization has been preparing for some significant changes. RubyConf, our flagship annual event, is also moving and adapting…

rubycentral.org

If you want to help, Joel. Then help. If you want to report accurately, then report accurately. If you want to misrepresent, attack, threaten or silence, I cannot stop you. But don’t try to pretend it’s something else.

By not amplifying that (new to many) information. You are showing me either you already knew and chose not to mention or you didn’t and don’t feel it looks good for the team you chose. Instead you attack the messenger (me).

It’s almost like you took my exact position and reversed it. And deliberately linked to a different thread. Great “reporting” Joel. Very “fair and balanced.” Fox News would be proud.

Happy holidays from RBQ Conf. We’re grateful for all the early support, and excited to share our keynote speakers for March. CFP is open for two more weeks if you’d like to join them on stage. Rare tickets are still available. Details at rbqconf.com

Bild

Letting Puma auto-set your worker count is the easiest way to go for 90% of usecases. Currently, you can only do that with WEB_CONCURRENCY=auto, but we'll also make this possible in the next puma version by using `workers :auto` in your puma.rb.

If you are using Concurrent.physical_processor_count or Concurrent.processor_count to set your Puma/Unicorn worker counts, that is wrong. Use Concurrent.available_processor_count. It takes into account cpu quotas in envs like k8s/docker.

Bild

RBQ Conf is officially cookin’. Our CFP is open, and we’re looking for sponsors who want to support a warm, community-first Ruby gathering in Austin. If you’ve got a meaty idea to share—or want to help bring year one to life—we’d love to hear from you. rbqconf.com

Bild

“We adopted #rustlang for its security and are seeing a 1000x reduction in memory safety vulnerability density ... with Rust changes having a 4x lower rollback rate and spending 25% less time in code review, the safer path is now also the faster one.” security.googleblog.com/2025/11/rust...

Rust in Android: move fast and fix things

Posted by Jeff Vander Stoep, Android Last year, we wrote about why a memory safety strategy that focuses on vulnerability prevention in ...

security.googleblog.com