After several months of work, we finally enabled Pitchfork reforking on 100% of Shopify's monolith. ~30% reduction in memory usage, ~9% better latency and more!.

RT @peterzhu2118: I just published "Implementing Embedded TypedData Objects" about a feature @_byroot and I worked on for Ruby 3.3. A bit l….

I wrote a post to braindump what I'm currently working on: allowing lock-free access to class instance variables from Ractors.

I did some sort of rubber duck blogging about a patch I'm currently working on:

Some personal thoughts on the usability of MySQL and PostgreSQL protocols:.

Here we go. That one I really needed to get of my chest for the better part of a year, so I feel relieved now. It's really long but hopefully not too hard to follow.

This is the last subject I wanted to talk about before I can start talking about Pitchfork itself. What I think Ractors are useful for, and why that isn't writing web servers:.

Continuing my series to give context on Pitchfork design, why I think HTTP2 support isn't important (for a Ruby application server).

RT @takkanm: 🚀 httpclient gem 2.9.0 is out! 🚀 After 8 years, we're thrilled to release this update thanks to amazing contributors! Huge tha….

One more entry in my series to give context to Pitchfork design.

I wrote down my personal thoughts on whether it's worth removing Ruby's GVL and what it would take. I wanted to talk about Ractors too, but this is already too long, so that's for another time.

@LattaAI Also I'm pretty sure bots are supposed to register as apps on @github so you are probably breaking their TOS.

Hey @LattaAI, I never asked anything so if you could keep your AI bots from posting garbage comments and patches on my repos that's be great. Thanks.

Before I can talk about Pitchfork, I obviously have to talk about fork. If you ever did some system programming you likely won't learn much though.

RT @siaw23: .@_byroot from Rails and Ruby core and senior staff engineer at @ShopifyEng, joined me on @railschangelog to talk everything ab….

I want to write a post about Pitchfork, but before I can get to that I need to share some thoughts. I suspect this one may be more controversial than the optimizing JSON series 😅.

RT @k0kubun: Ruby 3.3.7 Released This is a routine update that includes minor bug fixes. We recommend upgrading yo….

It is done, I finally concluded the ruby/json optimization series. I hope you enjoyed it:

Here's most of the parsing optimization covered, only one extra part and the series should be over. But I have ideas of further topics.

RT @paracycle: @eightbitraptor wrote about the new Modular Garbage Collection in Ruby 3.4, how it works and what it means: .

Part 5 is out, I'm finally done with the encoding side, so next time I can start talking about parsing:.