nikitonsky: Ultimately, it all comes down do a simple question: are you writing for your readers, or are your readers here to fulfill your marketing needs? What comes first?

Here’s a final muse for current year. This probably counts as wise posting. On local news there’s sentiment that the world is now “post–truth”… but historically; since when has the world not been post–truth? Truth (verifiability/provability) is ultra rare and trust abundant :-)

The Internet/Blockchain/whatever is not a truth machine and could never be a truth machine. Inside events/stories/happenings everyone’s just as clueless as in past eras and technological differences become “functionally equivalent” — meaning you either waste time separating signal from noise in “fast” and “fake” information infinitum or waiting for “slow” and “official” carrier pigeons to arrive.

Polar bear in Svalbard, Norway (© Dennis Stogsdill/Getty Images)

Lake Powell water levels, using an Internet data source.

Lake Mead Water Levels, using an Internet data source.

New Year’s Eve fireworks, Sydney Harbour Bridge, Australia (© Wendell Teodoro/Getty Images)

Rock formations in the White Desert, Egypt (© Anton Petrus/Getty Images)

I’ve since realized that Hugo’s architecture provides a variety of template optimization strategies. Hugo builds pages concurrently, so it might be hard to see on a modern device but before partialCaches or module mount trickery — there’s still the implicit complexity of the output/lookup model.

Generally the complexity cost of the default output formats are: page > term > taxonomy > section > home. Keeping expensive calls inside a section and/or a home template is usually optimal. i/o and maybe memory should be the only problems with lots of pages.

nikitonsky: Developers! Sort your lists. Thank you

A pair of silver-studded blue butterflies (© Misja Smits/Minden Pictures)