miniblog.

The games console market is fascinating: there's incentive to *not* provide upgraded models. You want the guarantee that a game for $X just works on any $X purchased. E.g. the Switch OLED has a bigger screen, and a better CPU than the original, but it's downclocked to match the original Switch's CPU.

I've been writing docs for different programming language operators (+, *, == and so on). Each one gets a separate web page. I've suddenly realised that / is much harder! docs/+ and docs/== is fine, but docs// just doesn't work as a URL in a static site. Any ideas?

When writing long-lived programs (daemons etc) in Rust, I find myself asking *where* I should put data. In a GC'd language it's just "I have a string" but Rust forces me to find somewhere to put it. You do get a performance benefit for this work though.