That’s because you know cron. If you knew timers equally as well they would be easier. And they let you handle the edge cases (retry, randomness, tracking, logs etc) without the need for a custom script.
Once you factor in the production edge cases I think timers are clearly easier. You get all of it for free.
I think if you know cron from the start it can be easier, but it gets really annoying really fast.
Compare:
0 0 * * * /usr/bin/flock -n /tmp/myjob.lock bash -c 'sleep $((RANDOM % 3600)) && /usr/local/bin/myjob.sh'
To:
[Timer]
OnCalendar=daily
RandomizedDelaySec=1h
That and things like systemd preventing overlapped delays, handing what to do if the system was down during the last cycle, built in logging and event tracking. Seeing successful vs non successful runs etc.
Once you add in those production requirements cron gets annoying fast and timers are easy.
The main functional difference between systemd and others is that systemd will just work. Others will require you hand tune and hand tinker with a non-mainstream Linux distro.
If your hobby is init systems by all means mess around though.
I personally quite like systemd. Unit files are clean, timers services and sockets are easy to manage etc.
Honestly it’s a non-problem. Best advice is to use what is best supported. Don’t let the extremely fringe (but loud) tiny group of systemd haters throw you off.
Imagine being this ignorant. They chose to fork only office because it’s web based and AGPL.
The original only office team refuses to allow community contributions and tries to stop people from forking it with a stupid (against the terms and spirit of the AGPL) poison pill.
Eurooffice are the good people here.
Fedora with Niri on laptop / desktop.
Alma Linux on servers.
Out of curiosity what mandatory features would you consider missing?
Yah but community centric GPL to no copyright is sort of the goal for the recent slop rewrites.
If there is no copyright on the slop output code based on GPL code that’s a win for the corps.
I think you’re mixing things up here. Mac’s are actually VERY performant, both objectively and relative to the on board ram.
There are many critiques that can be made of macOS. But saying it runs inefficiently is not one of them.
Maybe in 2019. In 2026 8Gb of ram alone costs $150
Can’t tell if cult member or troll. Either way the comment is of 0 value.
The same applies to this guy. His work is quite impressive, but his antisocial tendencies got him booted from working in the kernel. And now he’s gone down this path.
Hopefully things level out before we see a templeOS level mental health crisis situation.
It’s all about friction. As long as the user has to pick an instance they will always hesitate to pick any federated service. The average user will always choose the path of least resistance.
Proprietary services spend a lot of time trying to reduce friction, and it works.
The only solution I can think of would be a three part one:
This would of course require some federated account login system. Hard but not impossible. It could be some sort of Casandra style ring based account service where nodes are part of the ring.
This eliminates the new user friction.
It works anywhere any time with corpo style low friction. You don’t need to think about instances at all till you are ready to.
Look at the Jellyfin one. Why is there something breaking the logo from the right? Lots of little things.
Fair. It’s not just that one though. I notice a lot of weird things there.
But I responded to a comment cursing out systemd on a post about system V being dropped?
The comparison is as made because the comment brought up systemd on a post about system V.
Why post this ai generated content? Since when does the docker logo have the Cassandra eye in it?
Yah! Screw them 20 line unit files. We roll with 500 line bash scripts.
/sarcasm
I mean yah? That’s obviously true. That’s why I said it was close to actual anti semitism. Not bona fide antisemitism.
This is weirdly close to actual anti semitism. Israel is a genocidal state, reasonable people can agree, but there being a secret plan to control the world reaks of something more dog whistle-ish.
I can see how for some people cron is more straightforward to learn, at least till you need to handle logging, checking for cron results, handling when the triggered event can’t happen that instance, ensuring only one instance of the triggered thing happens at once, adding time jitter, etc.
Then timers are way simpler. Timers let you create robust timed events for free. With cron you need to do all that yourself.