That rule is plain wrong. Not everything compose well enough to make pipelines or configure with some booleans and numbers and strings. Sometimes you need cus

That rule is plain wrong. Not everything compose well enough to make pipelines or configure with some booleans and numbers and strings. Sometimes you need custom behaviour. In fact, most of the time you want custom behaviour, or just minor modifications or hooks. IDK what uses there can be for custom behaviour in a cron task, but that is the key: that you can not know every use case before hand. And instead of fighting with users over what features and configurables to enable, allowing them to do what they want is just easier and better. Moreover, "a simple task scheduler" is a simple task scheduler. It's written in 1500 lines of scheme code, another commenter quotes.