What makes jobs "tricky" is that jobs are--by definition--entirely side-effects. So: - What happens if the process where you called the job crashes? - What

What makes jobs "tricky" is that jobs are--by definition--entirely side-effects. So: - What happens if the process where you called the job crashes? - What happens if the entire application crashes? - What happens if two threads/processes schedule the same job? - Should jobs be stored in memory? On disk? In a db? Are all sort of interesting questions. Presumably the Deno runtime deals with this in a way that's opaque to the user, but that using "a library" does not, especially in a language like Javascript where processes/jobs are not really first-class.