Slow clap everybody: I rendered the 3D route animation with 16 instead of 32 samples per image in order to get it done in an afternoon rather than overnight. #rayshader #rstats

Oh, that's nice!

Makes me want to hit the slopes!

Nice! Especially the note on how the artists handled snow.

Is there going to be any details at SIGGRAPH 2026 about your wavefront-optimized nesting dielectrics implementation? That sounds like interesting work.

I guess “develop new GUI backend package” is on the to-do list, ETA 2035 at my current dev tempo 😜

Ahh! That’s even worse!!

Smart choice not updating. I enjoyed reading this post; really got at the UX issues with Tahoe.

What's worse: Tahoe broke XQuartz and I have to rgl_widget() as a workaround. 😠

Really giving that denoiser a workout!

I only mentioned HDR because the additional ~4 stops of dynamic range on HDR displays could make such a plot more interesting, especially if you split the "standard exposure" times by day/night. I've been working on a day/night atmospheric simulation package and using EXR output has been helpful.

Not taking them in HDR, but rather using the gain/exposure information to generate a "radiance keogram": a consistent look at the average brightness (energy received on the sensor) over the year.

Is the gain set ahead of time, or adapted to the scene? It would be interesting to see an HDR version of this plot: one with constant exposure through the year (scaled up so the 0-0.25 lux variation of the moon is visible).

"If everyone is special, no one is." - The Incredibles

Left: macOS Tahoe
Right: imaginary macOS Tahoe where apple still cares about design

The most amateur part is the consistency issues noted in the blog post: you can see clearly that some higher up decided everything needed to be an icon but didn't put bother first developing a topdown strategy to implement it, so it was all cobbled together at the working level.