3 ms·
and allows configuration files to be written in scheme (as well as Vixie's original format) for infinite flexibility in specifying when jobs should be run. It
by userbinator 9y ago
and allows configuration files to be written in scheme (as well as Vixie's original format) for infinite flexibility in specifying when jobs should be run.
It looks like Greenspun's Tenth Rule has been taken to the next level. Software that's so configurable its configuration files itself are written in a Turing-complete language is the bane of enterprise development. IMHO if you need such complex requirements, that should be done by something other than the configuration file of what should be a simple task scheduler.
- bjoli 9y agoIt might just be me, but I like being able to use a scheme file instead of a bash file if I need more complex logic for the command to execute. It gives you standard vixie Cron AND the possibility to handle everything as a scheme program. You just put a scheme file in your Cron dir and have the logic in there. Really not much different from executing a shell file from regular Cron.
- fulafel 9y agoI guess calling Guile an "ad-hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp" could be a clever salvo in a religious war between Scheme and Common Lisp programmers, but of course Mcron's approach is heeding Greenspun's implied advice.
- sevensor 9y agoI think this is the crux of the argument between proponents of simpler init systems and proponents of systemd. We have complex requirements implemented in complex logic. Do we want that complexity baked into the init system, or do we want that in our configuration language?
- gkya 9y agoThat 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.
- spc476 9y agoBut it seems like in Mcron, you can schedule a job along the lines of "Run on May 27th, November 23rd and December 29th, but only in non-leap years and if the days in question fall on a Wednesday or Saturday". With cron, you would have to run the program ever day and the job itself is responsible for checking if it needs to do its action. Is that a silly example? Yes. Is it realistic? Perhaps. As the company I work for transitions to an "Enterprise Class" company, I'm seeing a lot of silliness in processes.