dshearer

Thanks for the congrats! Actually, it's not shipping quite yet --- it's still in beta.

Jobber is really just cron + support for error-recovery strategies like exponential backoff + support for getting the job execution history. It is very simple to deploy: it consists of just two (native) binaries, and has no dependencies (well, other than Bash).

Chronos also supports these additional features (although I don't know about exponential backoff), but Chronos is much more ambitious than Jobber. Probably the biggest differences are that Chronos supports farming jobs out to other nodes and that it supports dependencies between jobs. And of course Chronos has a nice GUI. On the other hand, I imagine it's a bigger deal to deploy, although I haven't done so myself.

So, if you have a bunch of related jobs that need to run on multiple nodes, Chronos would probably be best. Otherwise, try Jobber!

Best of luck on your startup! It looks like your goals for Ikura are more ambitious than mine for Jobber --- e.g., Jobber doesn't spawn multiple instances of a job like Ikura does.

(Jobber author here.) It's...interesting that this is the aspect that has gotten the most discussion so far. But thank you, jacquesm et al., for your feedback. I certainly don't want this to turn people away from Jobber, so I'll change it. Computers are frustrating enough; we don't need to add more aggravation!

On the other hand, IMO, the biggest profanity you can put in an error message is an error code and nothing more. Now THAT is how to mistreat your users!

I wonder if there were similar discussions about the insults sudo gives you on OpenBSD (http://prefetch.net/blog/index.php/2012/08/01/sudo-insults-w...)...