3 ms·

Ordering is a subset of temporal though. That is, ordering implies there must be a relative time between events. Absolute time doesn't have to matter, nor does

• CyberDildonics 3y ago
  Ordering is a subset of temporal though. That is, ordering implies there must be a relative time between events. Absolute time doesn't have to matter, nor does time between events. It's still temporal. It's only temporal because all execution is temporal. The fundamentals of what you are trying to achieve aren't when something executes, it is the order. If try to execute two different things at two different times, your synchronization could go wrong because that isn't really what you want, you want a guarantee of the order. If you try to synchronize by guaranteeing the order that operations execute it will work regardless of what time something executes. Ordering is what you are actually trying to achieve, timing in ancillary. That's why the title is 'time is not a synchronization primitive'.