Good to know

Nice. Have you tried avif? Should be even better.

The main point of reactive extensions is the temporal coordination.

I think you get a lot of that from the event stream concept. And I'm definitely not going it justice in my explanation of it.

My mental model of it is more like streams of events/data and associated handlers. The core concept are observables and observers that subscribe to them, along with a plethora of operators to fold, switch, map, throttle, sample, and so on.

Oh, I meant reactive extensions. I find Akka very straightforward, as do I their dotnet sibling Orleans. Amazing frameworks.

I'm a huge fan of the concept. In practice, I had a very hard time getting it to work, always ending up in crazy deadlocks. Obviously from a lack of knowledge of the framework, but at least I found the learning curve very steep.

I'm getting a little bit reactive extensions-vibes. In .NET we have AsyncRx (github.com/dotnet/react...) which seem to get close to what you're looking for?

I'm curious how that would look in a programming language. Do you have a good example of what you mean?

I stopped using Just-Eat altogether for that reason. They would consistently promise 35 minutes right up until about 5 seconds after payment, at which point the estimate was now 1 hour and 30. Needless to say, that would most of the time have been a deal breaker had I known.