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.

Blade CLI is a nice find. I saw a past iteration of this a while back in nsrosenqvist/blade-cli. Basically, it’s a cli for kinda rendering blade templates. Don’t ask why..

name: {{ $name }}
type: {{ $type }}

blade render data.yaml --name="name" --type="type"

I know of four PHP static site generators.

1. Jigsaw: Laravel Blade templates. Source Code
2. Couscous: Twig templates. Source Code
3. Sculpin: Twig templates. Source Code
4. Spress: Twig templates. Source Code

The key advantage is obvious: dynamicity “technically” comes for free. Feedback/debugging loops “can” be made instantaneous, and scaling to a large output is probably not too difficult.

One downside is that corporate minded developers and consumers online will think you’re a noob for choosing PHP.

WordPress has an affinity for back–doored radioactivity. If I can get my way (which is hard), a WordPress install has only 1 theme and 0 plugins.

wordpress/
|-- public
`-- wp-config.php

/* Disable installing plugins and themes */
define('DISALLOW_FILE_MODS', true);