My @sfrubyconf talk on real-time collaboration with AnyCable, YJS and Rails is up! I felt really happy with how it came out - let me know what you think because I can't watch myself talk 😂
https://t.co/q9aWicUa49
Super cool news tonight: Rails realtime now runs on the server of your choice 🔥🔥🔥
Vova’s Action Cable server adapterization PR was merged 🥳. Same Channel and Connection code, swappable runtime underneath: Falcon, Fibers, async-cable.
This is the groundwork AnyCable has been proving in production for years, now landing in Rails itself.
People credit Rails’ longevity to DX. I think the secret behind it is adapterization pattern: every layer hides a default behind an interface, so the framework absorbs each new wave of innovation without a rewrite. Others wire it up with extra services. In Rails you swap the implementation as you wish, keeping the code intact.
Two years in the making, with
@ioquatix, @matthewd and @rafaelfranca steering the reviews. Congrats @palkan_tula 🥳
Every engineer should read this.
The principles for building reliable software systems have been around for a long time. Max outlines them beautifully.
Here's to getting that 99.99% on your status page.
https://t.co/HFDcriLodl
@paolino@bradgessler Yea @_byroot put a ton of work into that, it's a huge win. I seem to remember seeing that 8+ does it... better? But it is a part of Rails 7.2 as well.
@paolino@bradgessler I think this + my batch support work https://t.co/42frT26HBT would be a crazy unlock for being able to coordinate IO workloads/LLM interactions. Fully parallelized tool calls with a batch checkpoint at the end
I think people are sleeping a bit on how much Ruby on Rails + Claude Code is a *crazy unlock* - I mean Rails was designed for people who love syntactic sugar, and LLMs are sugar fiends.
Currently in ActiveJob, `wait` in `retry_on` accepts a proc, but it is only handed the execution count. I think access to the error can also be useful when calculating the next wait time. If you agree, give it a like! https://t.co/dZwAaZtfhr
Currently in ActiveJob, `wait` in `retry_on` accepts a proc, but it is only handed the execution count. I think access to the error can also be useful when calculating the next wait time. If you agree, give it a like! https://t.co/dZwAaZtfhr
“It’s 10pm, do you know where your children are?”
I added this to my “when good threads go bad” post
Does anyone else remember these ads?! May have only been a USA thing
It’s late, and you get alerts that web requests are failing. Page loads hang endlessly. The server isn’t responding, requests are queueing up. What do you do?!
"When good threads go bad" is a deep dive into stuck threads, how to deal with them, and what to avoid.
link below