Debian ships the setting commented out, so a multi-gigabyte database runs on a 128 MB cache and burns CPU re-reading the same pages forever.
Without swap, the first allocation that cannot be satisfied is immediately fatal to something — and the kernel picks its victim by size, not by blame.
If every mistyped URL returns your home page with a 200, search engines will index all of them as real pages — and split your ranking across the duplicates.
A static sitemap.xml wins over any dynamic route, and a generator that walks the filesystem cannot see content stored in a database.
An hour lost to a two-megabyte upload limit that did not exist, because the value came from the wrong SAPI.
Page views, top pages and per-site traffic, from the file already on your disk — no JavaScript, no third party, no Elasticsearch.
Every quota you invent is a second number to keep in sync with reality. The filesystem already knows how much space there is.
If your "publish at" check only runs when an admin loads the dashboard, then a post scheduled for 6 a.m. goes live whenever somebody happens to sign in.
Writing, updates and how-tos.