When making hugo themes, it’s probably better defaulting to absURL and relURL over baseURL for links. It avoids most breakage on links that depend on a base and more easily allows multilingual support with absLangURL.

However realistically (for anything), interpretations of file, directory/, absoluteness, and relativity are varied. Testing artifacts for ≈ 100% internal/self linking consistency, under different conditions, and after every code change is better time spent debugging. Sub directories are exceptional cases… even now some of my links are broken except that my web server automatically fixes common mistakes (:

The Chrome experimental recorder tool has been around for a long while. I thought it was still mostly wip but I got schooled and apparently, this is a more faster way to jump–start a puppeteer script/test:

Which browser engine “paints” HTML the smartest on my device? In the clip below; Surf substitutes for Safari and Chromium for Chrome. My blog is the testee since there’s guaranteed cache control and jitter.

Surf and by extension Safari (or any Webkit–based browser) wins imo. Webkit feels smooth (sneakily, too smooth). It’s probably partly why Safari on macOS/iOS feels so fast. Chrome (not Chromium) is almost on par or so I’ve been told. Not exactly web dev but interesting huh?

Profiling is the nice, cozy, and lazy way to efficiency. There’s something neat about avoiding optimization and having the numbers to prove it relative to an initial baseline. In PHP there’s Xdebug and KCachegrind and I recently saw php-spx in my feeds. A profiler in any language environment with snapshots of performance over time is just — well nice. The terribad situation is not understanding exactly how something became slow. It might be too late then.