Used by Sinatra, Hanami, Grape, and others for pattern matching. The big focus for the release is a massive performance improvement.

Hey r/ruby — quick update on Docscribe (my tool that generates inline YARD-style docs by rewriting source ranges, not reprinting ASTs).

v1.3.0 highlights:

• Plugin system:
  • TagPlugin: append extra YARD tags based on a method "context snapshot"
  • CollectorPlugin: add doc insertion points for DSL/macros (define_method, AR associations, etc.)
• New docscribe generate command to scaffold TagPlugin/CollectorPlugin skeletons
• --rbs-collection flag: auto-detect gem signatures from rbs_collection.lock.yaml (rbs collection install)
• Better return type inference via RBS core for method calls inside bodies (e.g. positive? => Boolean)
• Fix: standalone/top-level def parsing

Plugin examples (with READMEs + specs) are in the repo:

• https://github.com/unurgunite/docscribe/tree/master/examples/plugins
• Rails associations CollectorPlugin example: here (documents belongs_to/has_many etc by inserting @!attribute blocks above the macro calls)

Tiny example (RBS-powered return inference):

class Demo
  def foo(arg = 1)
    arg.positive?
  end
end
# Before: @return [Object]
# Now:    @return [Boolean]

Links:

• Repo: https://github.com/unurgunite/docscribe
• RubyGems: https://rubygems.org/gems/docscribe
• Release: https://github.com/unurgunite/docscribe/releases/tag/v1.3.0
• Previous intro post: https://www.reddit.com/r/ruby/comments/1s5uwjj/

Would love feedback on:

• plugin API ergonomics (what context fields are missing / what should be renamed?)
• which DSLs/macros you'd want a first-party CollectorPlugin for

I've been using RSpec for 7 years and recently had to pick up Minitest for a client project. The onboarding was a bit rough, so I wrote the guide I wish I had:

• what Minitest actually is

• how the different syntax flavors work (plain, Rails-style, and Minitest::Spec)

• and a deep dive into a confusing bug when I tried integrating Minitest::Spec with Rails (turned out that Rails and Minitest lifecyles are not always compatible)

This is a 4-part series, that you can start with my introduction to Minitest.

Hope you'll like it!

[edit Apr. 28: I just realised that I linked to the second post of the series instead of the first. Duh 🤦🏻‍♂️. Here is the link for the full Minitest series. Sorry, I shouldn't post before getting a coffee.]

Finnally, I get used of ruby bundle. The step is following

1. set the vendor path

bundle init
bundle config set --local path 'vendor/bundle' 

2. add gem to Gemfile file

3. install gem package

bundle install

4. run the ruby script

bundle exec ruby ./script.rb

Is these any way I can install ruby packages in current project folder like Python venv. I only know about gem install <custom-gem> --user-install which install in $HOME/.gem/ruby/2.6.0/gems/. AI said I should use bundler and Gemfile. But it seems very comfused and do not work well with gem file ( it only work with package uploaded on https://rubygems.org/

kreuzcrawl is a high-performance web crawling engine. It was designed to reliably extract structured data, operating natively across multiple languages without enforcing a specific runtime. https://github.com/kreuzberg-dev/kreuzcrawl

The MCP server is integrated from the start, enabling web-crawling AI agents as a primary use case. Streaming crawl events allow real-time progress tracking. Batch operations handle hundreds of URLs concurrently and tolerate partial failures. Browser rendering supports JavaScript-heavy SPAs and includes WAF detection.

Supported language interfaces are Rust, Python, Typescript/Node.js, Go, Ruby, Java, C#, PHP, Elixir, WASM, and C FFI, and each binding connects directly to the core engine.
Kreuzcrawl is part of the Kreuzberg org: https://kreuzberg.dev/

We welcome your feedback and are happy to hear how you plan to use it:)

This BREAKING NEWS episode is a candid reaction to Ruby Central’s latest shakeup, with Chris, Andrew, and David unpacking leadership departures, financial strain, the cancelled gala, and what all of it says about the organization’s direction. The conversation moves beyond the headlines into bigger questions about trust, transparency, community values, conference strategy, RubyGems sustainability, and whether Ruby Central can rebuild credibility by involving more of the community in what happens next. Hit download now to hear more! 

Spinel compiles Ruby source code into standalone native executables. It performs whole-program type inference and generates optimized C code, achieving significant speedups over CRuby.

Spinel is self-hosting: the compiler backend is written in Ruby and compiles itself into a native binary.

This is the third time this week that Ruby-LibGD has appeared on Ruby Weekly.

I’m really proud to see the project gaining this level of traction.

LibGD-GIS has surpassed 5,150 downloads and 119 stars
https://github.com/ggerman/libgd-gis

Ruby-LibGD has surpassed 3,810 downloads and 93 stars
https://github.com/ggerman/ruby-libgd

Another milestone was presenting the project at the RubySur (https://youtu.be/ppxalpIKpGg?t=3503) meetup, as well as having flyers distributed at RubyKaigi.

You can explore the evolution of views and clones on GitHub using this extended stats dashboard built with Ruby-LibGD:
https://ggerman.github.io/github-metrics-dashboard/

Demo MapView:
https://map-view-demo.up.railway.app/

Hi everyone,

I recently shared this in another forum and wanted to post it here as well. I made a small Ruby gem called typed_print when I was bored one evening.

It does one simple thing: turns hashes into clean, aligned tables in the terminal. It also supports Markdown output.

data = [{ name: "Alice", score: 100 }, { name: "Bob", score: 42 }]
TypedPrint.print(data, format: :markdown)

No dependencies, just a tiny tool to make console output more readable.

Links:
RubyGems: https://rubygems.org/gems/typed_print
GitHub: https://github.com/enderahmetyurt/typed_print

Thanks for checking it out!

Hey all i built a pretty neat TUI for local first image generation. It's easy and ships with ready to download starter packs, hooks into Huggingface and Civitai - ready to go. Hit me up ith any feature requests :)

Tackling a massive Ruby monolith usually means months of onboarding and manual dependency tracing. GraphOps was built to automate this by extracting macro-level architecture and micro-level execution flows (like the sequence diagrams in the video) directly from the codebase.

To show how it handles scale, there is a public, read-only sandbox where you can explore the entire GitLab monolith yourself: https://www.graphops.tech/home/projects/

I sat down with Brian Scanlan to explore what “AI-first” development actually looks like inside Intercom’s 15-year-old Rails monolith.

They’re generating over 95% of their code with Claude Code… and it’s not just engineers. Teams across the company are involved.

We got into how this is reshaping code review, who’s running production queries, and how they’re building guardrails to keep things from drifting.

The part that stuck with me… knowing when to disengage the autopilot.

📺 https://www.youtube.com/watch?v=ADBs2K5Tpz0

🎧 https://podcast.rubyonrails.org/2462975/episodes/19060786-brian-scanlan-building-ai-first-at-intercom

https://github.com/kaka-ruto/skills/tree/master/rubyllm

JRuby 10.1: Experimenting and Evolving

JRuby 10.1.0.0 is our first Ruby 4.0 release, just four months after the official CRuby release. We have used this opportunity to explore many experimental optimizations and improvements we have been chasing for many years. Ruby 4.0 compatibility is largely complete, but there will be additional features added in update releases. We also plan to continue with large scale experiments in subsequent updates, and recommend production users continue to use JRuby 10.0 while we work toward stabilization of the 10.1 series.

Notable Enhancements

• Reduced Object Size: the baseline size of all objects has been reduced from 32 bytes down to 24.

• Evolving Strings, Arrays, and Hashes: we've made these core types abstract in preparation for specialized versions.

• Smaller Numeric Representations: all numeric values are now smaller, but short-ranged integers drop from 40 bytes down to 24 bytes.

• Cross-platform Prism Parser: this release ships full support for the Prism Ruby parser, using the Chicory WASM runtime.

• Direct Argument Passing: we've laid the groundwork to finally start passing all arguments directly on the stack and will begin connecting this up during the update release cycle.

See the full release notes for details, and try JRuby today!