Ruby Weekly Issue #812 covers several Ruby ecosystem updates: a deep dive into Ruby Hash memory usage (2-4x more than Struct) with patches targeting Ruby 4.1, RuboCop 1.89.0's lazy cop loading for 10-25% startup speedup, redis-rb 6.0 with RESP3 protocol support and Ruby 3.2+ requirement, plus links on running code at Rails server boot, Ruby MCP servers in production, and using AI agents with Ruby scripts.
Questions this post answers
What changed in RuboCop 1.89.0 regarding startup performance?
RuboCop 1.89.0 now loads cops lazily instead of requiring all 600+ cops at startup, resulting in a 10-25% startup speedup. Previously, every cop was loaded on initialization regardless of whether it was needed for the current run. Ruby teams tracking RuboCop upgrades and their impact on CI times follow changes like this on daily.dev.
What are the breaking changes in redis-rb 6.0?
redis-rb 6.0 now uses the RESP3 wire protocol by default, adds first-class support for the Redis Query Engine and JSON module, and includes new commands for Redis 6.2 through 8.10. Ruby 3.2 or higher is now required, making it a breaking change for projects on older Ruby versions. Teams upgrading their Redis client can track redis-rb release notes and community reactions on daily.dev.
How much more memory does a Ruby Hash use compared to a Struct with the same data?
A Ruby Hash uses 2-4x the memory of a Struct holding the same data. Ruby committer Jean Boussier analyzed the layout changes from Ruby 2.3 onward and developed patches targeting Ruby 4.1 that could shrink small hashes to reduce this overhead. Developers optimizing Ruby memory footprint can follow Ruby internals discussions and upcoming 4.1 patches on daily.dev.