Ryan Davis, one of my personal gurus, has submitted a PR to Rouge, a project I’ve been tinkering with recently. As I’ve said on Mastodon, this is a perfect example of what I consider a great pull request: the description is concise and considerate, but only comments on the request – the changes themselves can easily be understood by simply reading the commits in order. It’s really great – and the discussion that it started should be interesting.
Speaking of Mastodon, this is where I learnt about
caffeinate, an Apple-provided OSS tool
to prevent a Mac from sleeping. So far, I’ve been using KeepingYouAwake, but as
it happens it’s been banned by our IT department recently. Good to know there’s a bare metal alternative available, if
need be. (Granted, since I’ll be leaving the company in two weeks, it doesn’t matter a lot for now.)
Interesting alternative to the official doc. I’m a very happy user of Dash, and I like to refer to the official version of any kind of documentation in general, but I must say that I’ve had issues with Ruby’s doc in the past couple of months. Could this good-looking alternative be better?
I’m intrigued by the introduction of CSS Nesting. It’s the only thing I miss from Sass, but it does seem to still have rough edges. I’d love to try it out, though.
Also found via a blog post shared on ruby.social, this is the kind of quality-of-life, very well thought-out feature that gets me hyped with every new release of Rails. Adding normalization on assignement is so trivial that it’s easy to overlook, but doing it right, in a way that pleases everyone – or at least pushes through the different sensibilities – is not that simple, as the conversation in the PR shows. Plus, having the finder methods take the normalization into account is the chef’s kiss. Love it.