Thibaud Guillaume-Gentil

📊 The 2026 Ruby on Rails Community Survey is open! 9 years of tracking the @rails ecosystem — and we need your input to keep it going. Takes just a few minutes. Please share with your team! railsdeveloper.com/survey/

Claude Sonnet’s p90 latency rose 44% in three weeks inside Zed. Today we’re launching Agent Stats: a weekly view of AI agent adoption and turn times in Zed. See the data, and what it can and can’t tell you about how people actually use agents: zed.dev/blog/agent-met…

SQLite doesn't shrink when you delete data. My 37 MB database was taking 6.9 GB on disk. auto_vacuum is OFF by default and nobody warns you. Here's the fix for Rails. hencf.org/blog/sqlite-au…

Herb v0.9 is here! 🌿 This release focused on stability, compatibility, and deepening Herb's understanding of HTML+ERB templates. Featuring Action View helper support, Prism AST nodes, new linter rules, a faster linter CLI, new language server features, and engine bug fixes. 🚀

Ghostty 1.3 is now out! Scrollback search, native scrollbars, click-to-move cursor, rich clipboard copy, AppleScript, split drag/drop, Unicode 17 and international text improvements, massive performance improvements, and hundreds more changes. ghostty.org/docs/install/r…

Ruby on Rails is probably the most token-efficient way to write a real web app together with agents that doesn't immediately fall apart with security holes and unscalable decisions. rubyonrails.org

Stacked Diffs on @GitHub will start rolling out to early design partners in an alpha next month. In the meantime, here's video of our progress so far: (h/t for @georgebrock + team for their awesome work)

@igor_alexandrov @heyhey @rspec @claudeai I literally spent 20 years telling everyone not to use rspec and factories BUT MANY DIDN'T LISTEN 😂. Turns out, like convention over configuration, it was preparing for the future (of many core dev laptops and AI).

Convention over configuration set the path for 20+ years of great training data for AI to use today. Not only does this mean agents do great with Rails, but also that squishy humans can quickly and confidently review the output without a jungle of distracting boilerplate.

Happy Friday folks. This mornings first prompt: "I would like you to do a honest review of your agents md file in this repository. This file is completely written for you and I think it is too verbose. And there are other aspects that can be inferred otherwise. Run through each section and give me an idea of whether it should be removed, updated, rewritten, to something a little bit more succinct."

Absolutely essential reading blog.julik.nl/2026/01/go-fas…

> Programming with AI is still in its infancy, and yet it has already redefined what programming will be about in the immediate future... I won’t pretend to have any answers here, just assorted thoughts. jorgemanrubia.com/2025/12/30/bac…

Finally, ruby-lang.org/en/ has a new design.

@rails @marcoroth_ Congratulations @marcoroth_! Keep up the amazing work! 🚀🙌

Congratulations @marcoroth_! The Rails Core team has announced Marco as the 2025 Rails Luminary. The Luminary award exists to celebrate those in the community who have significantly advanced Rails for the benefit of all, through contributions, gems, ideas, or knowledge-sharing, and Marco ticked all of those boxes this year. Read the full announcement here: rubyonrails.org/2025/12/17/mar…

Presenting the unofficial @dhh/@37signals Rails Style Guide based on the Fizzy source code 😁 gist.github.com/marckohlbrugge…

As promised: a video talking about how we architect Rails apps and Fizzy. Includes thoughts on Domain Driven Design, service objects, callbacks, and concerns. I will record more of these, but probably not as long!

Today's Fizzy deep dive is CSS "While the industry sprints toward increasingly complex toolchains, 37signals is walking calmly in the other direction." zolkos.com/2025/12/03/van…

Re: Unmaintained Turbo, some personal thoughts: - Turbo works great. We have used it successfully for several new products since it was extracted out of HEY. We have used every bit the library has to offer extensively in Fizzy (upcoming product), and I can't think of a current bug on my list to fix. In my experience, Turbo, and the rest of the Hotwire libraries, are incredibly robust. - Turbo is maintained. We merged 42 PRs into Turbo this year and released 4 versions, the last one as recent as 3 weeks ago. And there are several more commits already merged pending to be released. Shoutout to Sean Doyle and Bruno Prieto for helping to review many of the changes we have merged this year 🙏. - I don't believe that ever-expanding software results in better software. Not for products, not for libraries. Turbo is already a pretty big and complex library with a large API surface. If anything, I would be interested in shrinking, cleaning, and simplifying rather than adding new stuff. - In the frontend world, everyone has opinions and preferences about how to build interfaces. Current Turbo reflects 37signals’. It is very easy to consider a new feature desirable when observed in isolation. And it is very easy to end up with a mess when you try to satisfy everyone. Unless it is a terrific idea that works for most people most of the time, I would advise against accommodating new APIs in the current version of Turbo. Future major versions are a different story. - Because it is an intricate library with a big API surface, and because it is used by MANY, it is easy to introduce regressions when changing code. Just check the recent commit history and you will find some examples. We need to move carefully before merging changes, regardless of whether those are small bug fixes or configuration options. - The big backlog in the repo is not great. We should do something about it, but I don't think that necessarily implies merging a ton more of changes per week. To me, the real concern would be if the library was buggy or… unmaintained. - Everyone is as free to complain and grumble as to press the fork button and show the rest of the world how it is done. But please, don't just threaten with the latter. Go for it! Because it is the option that actually requires putting in work and effort, I am sure it will be enlightening. My two cents.

🍺 Today I'm proud to announce @MacHomebrew 5.0.0 bringing you download concurrency by default, official support for Linux ARM64/AArch64, timescales for deprecating macOS Intel and removing macOS Gatekeeper bypass behaviours. Read more at brew.sh/2025/11/12/hom…

Herb v0.8 is here! 🚀 The biggest release yet, packed with new language bindings, Linter Autofix support, Linter Fix-on-Save, a new `.herb.yml` config file, formatter improvements, Tailwind Class Sorting integration, and a ton of performance, tooling and LSP improvements! 🌿