I was mostly kidding. But the little bit that bothered me was the idea that ‘it is so simple here are 8 pages to barely scratch the surface.’
cron works fine for me. And if I ever have to work in an environment where I can’t use cron and systemd is available, then of course I will use it. Thus far that has never been the case.
Yeah, I think it’s just the way the blog post was written. When I was reading it I saw the first few paragraphs was basically “here’s how to do Cron with it”, and then everything after that was “here’s a bunch of other features it has that cron doesn’t and how to use those”
I don’t think that’s the wrong way to write this kind of article, but I could see it feeling overwhelming on a skim, because it may feel like you need to read the whole thing in order to get anything working. But actually only the start was necessary, and the rest was tasty feature pitch.
I’ve been doing this stuff for 30 years. The helpful blog post that took 8 pages of text to explain how to schedule a job just made me angry.
I think I am finally into greybeard territory even though my beard made the change a few years ago. Damn.
Why did it make you angry? Do you believe that there are other implementations that do the task better and simpler?
All of 'em. If a joke took 8 pages to explain, it wouldn’t be funny either. Lennart’s cancer can go, thanks.
I was mostly kidding. But the little bit that bothered me was the idea that ‘it is so simple here are 8 pages to barely scratch the surface.’
cron works fine for me. And if I ever have to work in an environment where I can’t use cron and systemd is available, then of course I will use it. Thus far that has never been the case.
I argue for a 5% cost-of-living adjustment for bad software, and I make sure it’s a separate line item so they know it goes away when systemd goes.
Yeah, I think it’s just the way the blog post was written. When I was reading it I saw the first few paragraphs was basically “here’s how to do Cron with it”, and then everything after that was “here’s a bunch of other features it has that cron doesn’t and how to use those”
I don’t think that’s the wrong way to write this kind of article, but I could see it feeling overwhelming on a skim, because it may feel like you need to read the whole thing in order to get anything working. But actually only the start was necessary, and the rest was tasty feature pitch.