I agree, a serious tool should be taking into account the length of the output delay and reducing effects to match the conditions. But you can still do some of it, sometimes.

On the contrary, I am currently scaffolding out the template projects for a new system at $DAYJOB and I'm seriously considering putting it in the CLI tool template.

On the one hand, these tools are going to be used for Serious Business™ but on the other hand... I owe it to 14 year old me. I'll probably add something to allow disabling it with a flag file that can be created with the tool or manually. ¯\_(ツ)_/¯

I love this kind of things the first time I see them but I would hate it in a tool used everyday

./myfancytool -disablefx

./myfancytool -showfx

Or have an "on first run only" configuration that disables it for subsequent usage of the tool ¯\_(ツ)_/¯