Ah, the good old squeak/smalltalk days. A few years back I worked on signals (or rather a static analyser for the editor to support signals) in squeak/smalltalk. The kind of signals those indie frameworks like angular and svelte now adopt trying to solve the problem of changepropagation you outline in your paper.

What i'm getting at is: For the places where other tools are better (like the UI example), we already have other tools (signals, observables, effects, runes,...). And for the places like client/server-communication: This is kind of where "call/return" usually shines.

> And for the places like client/server-communication: This is kind of where "call/return" usually shines.

The WWW would like a quick word with you. CORBA as well, if it could get a word in.

> we already have other tools (signals, observables, effects, runes,...)

We can build them. We can't express them. We can also build everything out of Turing Machines, or Lambda Calculus or NAND gates.