News for hackers. Stuff that matters.
Re:Systemd, 10 years later (2020) by CogitoCogito on Saturday January 08, 2022 @05:02PM (#29856844)
> Exactly.

> “Idempotent” is one of the key words used as a cudgel in this way. It’s great for the bullshit artist, as to a layman the dictionary definition is completely inscrutable.

Are you saying that being "idempotent" is completely inscrutable? Is it not a fairly straight-forward concept?

Re:Systemd, 10 years later (2020) by tremon on Saturday January 08, 2022 @06:24PM (#29857728)
If we're going to be pedantic, "idempotent" (or rather non-idempotent) as used in the description is rather vapid and meaningless. Idempotency is a quality that describes the result of an action; as such, only actions can be thought of as idempotent. Applying the word idempotent to any noun that does not describe an action (such as "dataflow" in this case) is meaningless.

What does it mean for a dataflow to be idempotent in the first place? What purpose does it then serve to describe a dataflow as non-idempotent? What they meant to say, I guess, is that the dataflow may contain multiple actions for the same unit, and that systemd makes no guarantees about the end state of the unit in such a case. But even then, it is the execution which should be described as non-idempotent, and not the dataflow.

Re:Systemd, 10 years later (2020) by int_19h on Sunday January 09, 2022 @08:25PM (#29869447)
That feels unnecessarily pedantic. If the sole job of entity X is to perform action Y, and it always performs this action idempotently, then why not describe X as idempotent? It's shorter, and it's clear enough. It might not be precisely accurate in the dictionary definition of the word - but natural languages also have DSLs, and those DSLs evolve to adapt to their use cases. Saying "thing that performs an idempotent action" over and over again is a waste of everybody's time.
Re:Systemd, 10 years later (2020) by Spooky23 on Saturday January 08, 2022 @07:01PM (#29858080)
In the context used, it’s fluff.