> Also has perfect permission management,

A note to developers: describing a component of your system as ”perfect“ is such a big red flag I won’t ever consider using it. The hubris…

I thought so too but it also reads like perhaps English is not the first language of the developer.

Nuances of how perfect can mean "a really nice experience" vs. "our implementation has no flaws" might not be so obvious.

habr is a good indication of esl.

point on nuance is spot on. the translation process often becomes an unintentional transformation process.

This reminds me of when I (a native english speaker), was speaking spanish and said I was glad someone could spend time with their kids. I was later corrected that the verb I used (prestar I think) for "to spend" had the negative connotation of "to waste". Oops.

Edit: this was in a religious context as a missionary, which reminds me that "perfect" in scriptures is also misleading to a modern native english speaker. Other, perhaps better words include "whole" and "complete". I wonder if that is a common synonym in other languages.

Docs are a bit sparse, hard to tell what support is like for these but seems a bit limited/new: - job dependencies, success/failure conditions, retry logic, etc etc - process/user impersonation/delegation - custom calendars and execution times "ie last business friday of the month"

Any reader seeing software described as “best” and “perfect” should exercise extreme caution

It’s probably just a translation error. The author probably doesn’t natively speak English.

Hmm best is a strong word. It depends on what you are after.

I couldnt find the DAG in the demo, or in the docs. Without that it seems a bit limited.

For my usecases I need a Job description language, and the ability to have dependencies (either job to job, or a job needs flag x to run on this machine)

Is there a design paper somewhere? Curious how this was accomplished (and what trade-offs / failure modes it has): "System uses a consistency sharding algorithm, lock-free design, task scheduling is accurate down to the second, supporting lightweight distributed computing and unlimited horizontal scaling"

Consider Argo Workflows.

The comparison choices are strange. XXL-JOB, but not Airflow or Temporal?

Best? How does it compare to temporal, it looks inferior.

I thought about Temporal as well… Until I saw that OpenJob supports Oracle as the backend. I mean… It must be superior then.

what I look for in job runners is: can I sync any job definitions done in the UI to a git repository back and forth - and how is it handling secrets. Openjob.io looks like an early iteration.

Does anyone know if this works on windows and Mac?

Why should you run it on windows and Mac? On the other hand would I expected it to run in docker nowadays

Why shouldn’t you? Maybe you have windows or mac specific workloads?

Why not? It’s written in Java.

Java, Go, PHP, Python...?

What a bizarre list of languages.

Not... C?

Shell out from Python and do what you want there

One wonders how this got 77 points as of me typing this. Seems suspicious.

No ALGOL 58 or Pony support ? No.