| Home page | https://tomstu.art |
| Mastodon | @tom |
| https://twitter.com/tomstuart | |
| YouTube | https://www.youtube.com/@tom.stuart |
| Home page | https://tomstu.art |
| Mastodon | @tom |
| https://twitter.com/tomstuart | |
| YouTube | https://www.youtube.com/@tom.stuart |
I realise I’m being slow here, but… can anyone help me to understand whether Rails 8.1’s structured event reporting has any relationship to making the default logs (requests etc) structured, or are the two concerns completely orthogonal?
You can use Rails.event.notify to report “business events”, but do you still — and will you always — need a gem like lograge or rails_semantic_logger if you want the default logs to be easily parseable? I’m confused about what the big picture is supposed to be.
Leo pointed out that C++20’s std::chrono overloads the `/` operator to provide date creation syntax. Surely Ruby can do better?
```
>> module ISO8601
Month = Data.define(:y, :m) { def -(d) = Date.new(y, m, d) }
refine(Integer) { def -(m) = Month.new(self, m) }
end
>> using ISO8601
>> 2025-12-29
=> #<Date: 2025-12-29 ((2461039j,0s,0n),+0s,2299161j)>
```
I tried to explain why I don't believe the recent accusations toward my former teammates, as well as how the Ruby and Rails Infra team at Shopify operates and why it can be trusted.
https://byroot.github.io/opensource/ruby/2025/10/09/dear-rubyists.html
I’ve been meaning to write a post about my perspective on Open Source and corporate entities. I already got the rough outline of it; however, I’m suffering from writer’s block, but more importantly, the whole post is a praise of how Shopify engages with Open Source communities. Hence, given the current climate, I don’t think I could publish it without addressing the elephant in the room first anyway.
Ages ago, when I was still a student, I taught myself Ruby on Rails for my senior thesis and fell in love. Fifteen years later, and I’ve used Rails at every job I’ve ever held in the tech industry. Fifteen years, and I still love Rails! But there’s something rotten at its core, and we share a name.

Ages ago, when I was still a student, I taught myself Ruby on Rails for my senior thesis and fell in love. Fifteen years later, and I’ve used Rails at every job I’ve ever held in the tech industry. Fifteen years, and I still love Rails! But there’s something rotten at its core, and we share a name.