> For example, annual jobs can be represented as a infinite looping program that sleeps for a year
Does your system actually implement true durable compute? Like I can restart my mac or stop the daemon and it's (apparently) not only smart enough to resume this process where it left off but also account for the time delay and reschedule the wakeup? Astounding if true— if you do what's your strategy for achieving it?
The project doesn't implement durable programs (yet!).
I've done some prototyping in the past, and came out of it feeling it wasn't quite the right thing to dive into yet. I mostly lacked clarity around what the concepts / syntax / ergonomics should be, because I didn't have specific use-cases in mind.
I don't see it as a "global" always-on feature, at the moment.
I'm intrigued by Membrane's approach (https://docs.membrane.io/concepts/programs/) - but I'm not sure if it's the right fit for this runtime. TBD!