[zobzu]

so... cron's a 200kb self contained C program, super simple, does one thing, and does it well.

Chronos is built on top of frameworks, needs a few services to run.

Certainly it has value, but marketing it as a cron replacement is wrong imo. Chronos is one of these "web-server-service-tool" thingie, but no, it's not cron.

[bitwize]

Every time I come across one of these heavyweight, dependency-encrusted "replacements" for basic Unix tools, I'm reminded of L33tStart[0], a fictional, satirical init(1) replacement I wrote about on Reddit -- a sort of parody of systemd.

Every day, in a bizarre manifestation of Poe's Law, L33tStart seems less and less a parody.

[0] http://www.reddit.com/r/programming/comments/14ay0r/hacker_k...

[adambenayoun]

Any chance you could open source L33tStart. Also what type of ponies were you using for your startups? Black or white ponies?

[andrewflnr]

Mostly pink and purple, is my impression.

[zobzu]

heh, you made my morning :)

[rsync]

Ding!

Complex, interdependent systems without slack. Now add production pressures. You have all the ingredients of a "Normal Accident"[1].

You should do the opposite of this.

[1] http://en.wikipedia.org/wiki/Normal_Accidents

[jargonjustin]

It's solving a rather different problem than cron, but it's a problem that many people first attempt to use cron to solve. It's a replacement not in the sense of being a better cron, but as solving a problem for which cron is often used inappropriately.