I think this is good for people who only have occasional need for scheduling. I’ve used cron enough that I appreciate its compactness and would find this cumbersome and difficult.
I find Cron to be one of the clearest and most elegant Syntax solutions out there. Like you only have to understand it once and can assume the rest from looking at it. That's super elegant
Cron is definitely not the biggest problem in my life. I've never had a problem with its format. I think this is a solution to a problem I don't have - and I tend to find that "English like" formats don't do me any favours.
At the end of the day, anyone using cron-type things should just learn cron syntax, it’s really not that difficult and there are a number of websites that you can use to assist or spot-check your work.
I’m always incredibly resistant to “human readable” for things like this because there is just too much ambiguity.
Cron is great and widely used—I’m not trying to replace it. This is just another option for situations where you need something more readable for non-technical users or when you want to store schedules in a database and display them in plain language. There are valid use cases for both approaches.
The goal is provide a format that’s user-friendly while still being precise enough for developers and systems to rely on. It’s especially useful for things like configurable schedules in apps, admin dashboards, or any context where end users and developers need to share the same language.
> Because memorizing 0 18 * * 1-5 is harder than understanding every day between monday and friday at 6:00pm
Really? Does “Every day between Monday and Friday” include Monday and Friday? One could think the days between Monday and Friday are Tuesday, Wednesday and Thursday.
Why people don’t just learn cron syntax is beyond me.
> Why people don’t just learn cron syntax is beyond me.
Because it looks like line noise, is unreadable to anybody not a UNIX/Linux admin, and is a standard in the same sense that the directory separator is the backslash on the majority of deployed desktops and servers.
More importantly: It’s also not extensible without being completely changed, which makes it a poor design.
Fluent builders can be trivially expanded to support new capabilities without breaking existing code or configuration.
Cron’s syntax was likely a quick and nasty thing thrown together by some student at Berkeley or wherever in the stone ages of computing. We shouldn’t be bound by these accidents of history in the same way we shouldn’t keep using Roman numerals these days.
> Why people don’t just learn cron syntax is beyond me.
Maybe the better question to ponder is why is it something that needs explicit learning. It's a basic task scheduler.
The *nix format hell in general drives me insane. Immensely glad for the recent-ish trend of lots of applications at least slowly adopting JSON and others as both config and output options.
essentially the answer is that after 40 years of polishing a 'basic' thing it's realized that there is near infinite nuance in use cases and workloads, even without feature bloat.
I think this is good for people who only have occasional need for scheduling. I’ve used cron enough that I appreciate its compactness and would find this cumbersome and difficult.
I find Cron to be one of the clearest and most elegant Syntax solutions out there. Like you only have to understand it once and can assume the rest from looking at it. That's super elegant
Cron is definitely not the biggest problem in my life. I've never had a problem with its format. I think this is a solution to a problem I don't have - and I tend to find that "English like" formats don't do me any favours.
How flexible is the syntax? Can I write whatever and have a chance it parses correctly?
That's nice but I don't think Cron syntax is a big of a problem, most of the time.
How does it handle “bi-weekly”?
At the end of the day, anyone using cron-type things should just learn cron syntax, it’s really not that difficult and there are a number of websites that you can use to assist or spot-check your work.
I’m always incredibly resistant to “human readable” for things like this because there is just too much ambiguity.
Cron is great and widely used—I’m not trying to replace it. This is just another option for situations where you need something more readable for non-technical users or when you want to store schedules in a database and display them in plain language. There are valid use cases for both approaches.
The goal is provide a format that’s user-friendly while still being precise enough for developers and systems to rely on. It’s especially useful for things like configurable schedules in apps, admin dashboards, or any context where end users and developers need to share the same language.
I appreciated the feedback and comments.
> Because memorizing 0 18 * * 1-5 is harder than understanding every day between monday and friday at 6:00pm
Really? Does “Every day between Monday and Friday” include Monday and Friday? One could think the days between Monday and Friday are Tuesday, Wednesday and Thursday.
Why people don’t just learn cron syntax is beyond me.
> Why people don’t just learn cron syntax is beyond me.
Because it looks like line noise, is unreadable to anybody not a UNIX/Linux admin, and is a standard in the same sense that the directory separator is the backslash on the majority of deployed desktops and servers.
More importantly: It’s also not extensible without being completely changed, which makes it a poor design.
Fluent builders can be trivially expanded to support new capabilities without breaking existing code or configuration.
Cron’s syntax was likely a quick and nasty thing thrown together by some student at Berkeley or wherever in the stone ages of computing. We shouldn’t be bound by these accidents of history in the same way we shouldn’t keep using Roman numerals these days.
> It’s also not extensible without being completely changed, which makes it a poor design.
Fair enough but let’s please not replace it with something where the literal first example in the GitHub read me is ambiguous.
> Why people don’t just learn cron syntax is beyond me.
Maybe the better question to ponder is why is it something that needs explicit learning. It's a basic task scheduler.
The *nix format hell in general drives me insane. Immensely glad for the recent-ish trend of lots of applications at least slowly adopting JSON and others as both config and output options.
> why is it something that needs explicit learning. It's a basic task scheduler.
You still have to learn what exactly this sort of software can understand and that is, imo, no less of a time/effort needed to learn cron.
essentially the answer is that after 40 years of polishing a 'basic' thing it's realized that there is near infinite nuance in use cases and workloads, even without feature bloat.
Cron syntax sucks. Cron is good for a few small use cases but sucks for real world scheduling.