Debian's /tmpest in a teapot

I agree there's likely a near infinite number of reasons why /tmp being on a RAMFS is a Bad Idea, and an equal number of reasons why it's a Good Idea (same with the anecdotes). I kinda agree with the article title that it's a tempest in a teapot. If the use case contraindicates the default, this particular configuration is trivial to change without even a reboot. If you need a whole fleet of deployments, there are tools to manage configurations before creating the deployment image.