dumblob

Initially I thought "multiple backends" means to **guarantee** storing it to **all** of them. I.e. adding (changing) anything will wait untill it gets written to all backends and first then...

Maybe allow some manual intervention by letting the user to choose node(s) and "fix them in place" (to slightly clean the "mess" you write about)?

Let's discuss general concepts in the other thread first and see where it goes: https://github.com/til-lang/til/issues/8

Isn't the Actor Model rather expensive **in practice** (both performance-wise **as well as** code-bloat-wise)? If you have any specific API in mind, go ahead - I'm all ears to see...

If we decide to pursue something like those processors I outlined in https://github.com/til-lang/til/issues/8#issuecomment-844963543 then we might enforce every processor to get (and thus to handle) an "interrupt channel" akin to...

>probably, and implement common behaviors Erlang-style, like supervisors processes. This is actually **the** thing I'd rather get rid of (that's one of the reasons why I described "processors"). There are...

Ok, sounds like a lot of typing to me objectively. Subjectively it definitely feels like more burden than necessary as most of the command invocations are short and thus become...

Ah, thanks for explanation. I didn't know `math` accepts more than one argument. Is the rule "it's up to each command to group or not SimpleList's values" common for **all**...

> `math (\() [proc1 $x] (\) + \() [proc2 $y] (\) * \() [proc3 $z] (\)) - (\( $a / \( $b * 5 \)\))` - no idea where this...

> `math` accept one argument **today**. That's not a rule. But I want it to be able to handle multiple arguments. Thanks for explanation. I'm looking forward to `math` accepting...