A programming language idea: no static code, explicit caller context (Kite)

[Bienlein]

On Wednesday, 29 April 2026 at 18:16:11 UTC, Marconi wrote:

> Kite:
> You call a method and know exactly who called it (caller)
> You can return values normally
> You explicitly propagate:
> memory allocation
> errors
> execution context

Okay, and how do processes exchange data? Actors are a problem, 
because they are asynchronous. They have a mailbox which 
processes messages in the order of arrival. But it remains 
asynchronous programming to some extend with all its problems. 
Actors work well when exchanging messages between remote 
instances (see https://akka.io), because of the idea of 
supervision. If two actors that communicate with each other 
realize that somethin when wrong, some supervision actors resets 
them both and restards the operation.

But back to Kite. You might want to have a look on concurrency in 
Go based on blocking takes on channels. There are various videos 
on Youtube that explain this. This is called "communicating 
sequential processes" and was invented by Tony Hoare. I think 
this is pretty much as good as it gets.