[marcell]

I'm trying to understand how this would actually work. A lot of app development for a mid-size CRUD app is around encoding business logic and handling edge cases.

Let's take a specific example. Say I'm writing a software to help manage weekly CSA (box of veggies) deliveries. Sometimes a driver will miss a delivery, and in that case, you want three options:

(1) Fully refund the customer for that week

(2) Let them another receive another delivery the next day

(3) Give them company credit

If (2) happens, the driver component needs to receive a notification for the next day delivery.

Is this in scope of dry.io? If it handles this kind of thing, how?

[nickcassimatis]

Yes. We have an event language where you basically can say "IF X happens do Y".

[weego]

Hey that's how Watson handles AI too

[IshKebab]

Sounds like normal programming...

[nickcassimatis]

The idea is that in many cases how an edge case is handle is up to the person requesting the software. So unless you build an AI that can read minds there needs to be an easy way to express what their preferences are.

[C1sc0cat]

Oh I remember that it ran on CBM 8096 back in 81 - I seem to recall it was called "The Last One"