4 ms·

KCSS (Keep Cron Simple, Stupid)

• coldtea 12y ago
  Why? Because "change is bad, mkkkay"? It's not like Cron covers all our needs... The "do one simple thing and do it well" principle worked best for the simple needs of late '70s OSes. In 2014 it ends up with MORE (not LESS) complexity, built on top of those simple tools to coordinate them to do anything useful. And of course they're not even that smart in how they work together... Like "make" has grown configure and autoconf and all that cruft (because we "kept it simple").
  • faragon 12y ago
    Cron already covers all my job scheduling needs, yes. You can do all the "recover thing" in the scripts called by cron, without the need of complicating 99% of cases that don't need such complication. "Keep it simple, stupid" is still valid for 2015, in my opinion. About your off-topic comment: autoconf/automake adds crazy complexity. I avoid it as much as possible, using just Make (it allows you context detection and lots of conditional handling, without complicating things).
  • feld 12y ago
    autoconf is insane. Just write your own configure script... Keeping it simple does not need to cause abominations like autoconf. I was glad to see the new ntimed project is not using it. Here's a comment from the custom configure script: # Handwritten configure script. # ============================= # # Before you suggest I use tools for this, please read: # # https://www.varnishcache.org/docs/trunk/phk/autocrap.html # and # http://queue.acm.org/detail.cfm?id=2349257 # from https://github.com/bsdphk/Ntimed/blob/master/configure https://github.com/bsdphk/Ntimed/blob/master/configure
  • sre_ops 12y ago
    Yes, change for the sake of change is bad. Cron has a couple of problem - - 1 is fine-grained scheduling. - 2 ability to set jobs to "catchup" or to skip on failure. Cron has no other real problems. Complexity is always bad. Always.