Planning to migrate my jhawthorn@ruby.social account to john@hawthorn.pub over the next couple days 🤞

Made a PR with the delegate optimization stuff. Just need to fix the builds now 😭 https://github.com/ruby/ruby/pull/10510

I had an awesome time at @tropicalrb 🇧🇷 . Met amazing people and had great food! I hope I get the chance to visit again soon.

@jameskerr It's a scale that gives you more accuracy (most often seen on calipers) https://en.wikipedia.org/wiki/Vernier_scale

Worked more on optimizing delegates with @jhawthorn today. There are more edge cases that I thought there would be (of course), but I'm testing it in work CI rn. Anyway, I really hope we can land this in Ruby 3.4 (I'm confident we can)

I'll be on @tenderlove's channel in 10 minutes hacking on Vernier https://www.youtube.com/watch?v=ELa9vgPA1B4

Doing a live stream this week! I'll have @jhawthorn on as a guest, and we're going to hack on Vernier. We'll do it this Friday at 10:00 PDT (17:00 UTC), please join if you have time! https://youtube.com/live/ELa9vgPA1B4

Worked on an optimization to delegate methods with @jhawthorn today and I'm pretty excited about the progress. Need to fix more tests before I can land this patch, but I'm very happy about where it is and hopeful it will unlock other optimizations

✨📣The RailsConf 2024 program is officially live! ✨📣

Check it out now 👉 https://railsconf.org/speakers/

Say congrats to these amazing speakers 👏

Then register to join hundreds of Rubyists as we celebrate Ruby on Rails in Detroit on May 7-9!

🎟️ https://ti.to/railsconf/2024

Don’t miss this chance to learn, network, and explore Detroit's iconic museums, street art, food and music scene -- at the world's largest gathering of Rails developers.

Prices will ⬆️ after March 31 so don't delay!

@tenderlove I've also wanted^Wmeant to write a similar blog post for like 5 years so safe to say I'm not going to

Imagine a development environment where you can't use CI, you need to do code archaeology for an unknown number of revisions. Patches, repros, tests, announcements, must all be done in secret. Then, if you did it right, the absolute best outcome you can hope for is that everyone upgrades and they notice no changes. It's extremely high risk (no CI, done in secret), low reward (nobody is stoked they have to upgrade bc security)

Doing security releases sucks (don't worry, I'm just thinking back to the most recent Rails release). Was thinking about writing a blog post that explains the challenges, but even thinking about it makes me tired

Just published the RubyKaigi 2024 speakers list. See who are speaking... and who are keynoting! https://rubykaigi.org/2024/speakers/ #rubykaigi

@jared I think that's because this is how the text is perceived by locals.

@alexanderadam Thank you for the support!

@byroot Thanks! I hadn't seen that great tip!

@jhawthorn I couldn't watch live cause it was too late for me.

But after watching VOD, I wonder if you've seen https://github.com/mame/rubyfarm-bisect

Would have made your bisecting much easier I think.

Opened the bugtracker issue and patch from yesterday's stream

https://bugs.ruby-lang.org/issues/20285
https://github.com/ruby/ruby/pull/10037

Going live with more Mastodon hacking https://www.twitch.tv/jhawthorn

Partly due to streaming technical issues didn't fully get around to what I wanted to. Hoping to try again Monday (or later next week)