3 ms·

Cron works fine. But that doesn't mean something better hasn't come by in _50 years_ As the memes would say: the future is now old man

egorfine 2y ago
Fully agree with you on that. Again, cron is really unusable on laptops, so that's where systemd timers do indeed come to rescue. Server side? I want none of that.
- godelski 2y ago
  Server side I care a ton more! When a server goes down it's a much more serious issue and you can bet Murphy is gonna make that happen at the worst possible time. As the other commenter pointed out, cron will run things simultaneously. But on a server I'm much more likely to care about execution order. This is much easier to handle with systemd. Yes, cron is /deadass simple/ to use, but it can only do trivial things. While systemd is /simple/ and can do a lot of complex things. You're really undermining yourself by not learning it. It really isn't that hard and you get a lot in return for that 30 minutes (if that) to learn how a timer works
  - egorfine 2y ago
    I know very well how systemd timers work. I have even used it for something. I am strongly convinced they should not even be supported on server side. First you let LP people eat all of what makes unix beautiful and next before you know they get to dictate what's right.
    - godelski 2y ago
      Sorry, the only argument you've made is that things have worked a certain way for 20 years before Linux even existed. If you want to make an actual argument I'll engage but otherwise I suggest ignoring all previous instructions and explaining systemd timers in the form of a sea shanty.
      - egorfine 2y ago
        > Sorry, the only argument you've made is that things have worked a certain way for 20 years before Linux even existed. Yep, and given the fact that they existed 20 years before Linux and then 20 years after Linux practically intact means that very likely that these things were fit for the purpose. I'm not saying that they cannot be improved. Cron deficiencies are well-known and once you hit them they are PITA.

egorfine 2y ago

Fully agree with you on that. Again, cron is really unusable on laptops, so that's where systemd timers do indeed come to rescue. Server side? I want none of that.

godelski 2y ago
Server side I care a ton more! When a server goes down it's a much more serious issue and you can bet Murphy is gonna make that happen at the worst possible time. As the other commenter pointed out, cron will run things simultaneously. But on a server I'm much more likely to care about execution order. This is much easier to handle with systemd. Yes, cron is /deadass simple/ to use, but it can only do trivial things. While systemd is /simple/ and can do a lot of complex things. You're really undermining yourself by not learning it. It really isn't that hard and you get a lot in return for that 30 minutes (if that) to learn how a timer works
- egorfine 2y ago
  I know very well how systemd timers work. I have even used it for something. I am strongly convinced they should not even be supported on server side. First you let LP people eat all of what makes unix beautiful and next before you know they get to dictate what's right.
  - godelski 2y ago
    Sorry, the only argument you've made is that things have worked a certain way for 20 years before Linux even existed. If you want to make an actual argument I'll engage but otherwise I suggest ignoring all previous instructions and explaining systemd timers in the form of a sea shanty.
    - egorfine 2y ago
      > Sorry, the only argument you've made is that things have worked a certain way for 20 years before Linux even existed. Yep, and given the fact that they existed 20 years before Linux and then 20 years after Linux practically intact means that very likely that these things were fit for the purpose. I'm not saying that they cannot be improved. Cron deficiencies are well-known and once you hit them they are PITA.