John Hawthorn
@jhawthorn.com
Writing code for @Shopify, Rails, and Ruby. Previously @GitHub.
he/him | Victoria, BC | jhawthorn.com
he/him | Victoria, BC | jhawthorn.com
It happens before the value is assigned (and it seems like "frozen" Atom objects are mutable)
October 30, 2025 at 9:50 PM
It happens before the value is assigned (and it seems like "frozen" Atom objects are mutable)
That's on self, it needs to be done on the value being swapped
October 30, 2025 at 9:30 PM
That's on self, it needs to be done on the value being swapped
Parsing (of whatever) with a short lived is probably currently the most obvious win. Things where the data-in is simple and data-out is complex is a good place to look. ViewComponent is the opposite of that, and it's only slow because of its own implementation, I don't really see the benefit there.
October 30, 2025 at 8:31 PM
Parsing (of whatever) with a short lived is probably currently the most obvious win. Things where the data-in is simple and data-out is complex is a good place to look. ViewComponent is the opposite of that, and it's only slow because of its own implementation, I don't really see the benefit there.
I don't think 3.5 changed what was possible but the Ractor::Port API made a bunch of things a lot more ergonomic (also that and everything else is much faster and less buggy)
October 30, 2025 at 5:51 PM
I don't think 3.5 changed what was possible but the Ractor::Port API made a bunch of things a lot more ergonomic (also that and everything else is much faster and less buggy)
Ratomic is a totally fine experiment, but it totally breaks the ractor guarantees and should not be used. It _can_ crash now and is likely to crash more in the future (see eregon's issue)
October 30, 2025 at 5:51 PM
Ratomic is a totally fine experiment, but it totally breaks the ractor guarantees and should not be used. It _can_ crash now and is likely to crash more in the future (see eregon's issue)
No way, the Blues Jay will take it back to Roger Center
October 16, 2025 at 3:53 AM
No way, the Blues Jay will take it back to Roger Center
You're absolutely right...
September 30, 2025 at 12:53 AM
You're absolutely right...
There's totally room for them and if you like them you should use them and make more. It's not a value judgement. There's just something about them that doesn't appeal to me as a matter of taste vs. a traditional command line tool.
September 22, 2025 at 2:15 AM
There's totally room for them and if you like them you should use them and make more. It's not a value judgement. There's just something about them that doesn't appeal to me as a matter of taste vs. a traditional command line tool.
I think you're right about the forcing function. It also probably enforces a consistent look and feel. But that just suggests to me it's not the optimal version of what it's trying to be. A native GUI could and should be drivable 100% by keyboard
September 21, 2025 at 5:21 AM
I think you're right about the forcing function. It also probably enforces a consistent look and feel. But that just suggests to me it's not the optimal version of what it's trying to be. A native GUI could and should be drivable 100% by keyboard
I don't mean to single out bat, I think it's just the first tool that crosses the line. Something like `lazygit` is maybe a clearer leap. It's obviously a good tool people like, but as a fan of the command line I don't get why one would prefer that over the same tool as a full graphical GUI.
September 21, 2025 at 2:05 AM
I don't mean to single out bat, I think it's just the first tool that crosses the line. Something like `lazygit` is maybe a clearer leap. It's obviously a good tool people like, but as a fan of the command line I don't get why one would prefer that over the same tool as a full graphical GUI.
