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

[Marconi]

On Wednesday, 29 April 2026 at 17:56:56 UTC, Richard (Rikki) 
Andrew Cattermole wrote:
> What you described is actors.

Kite and the Actor Model are similar:
No hidden global state
Clear ownership of behavior
Encapsulation of logic inside entities (objects/actors)

The key difference:
The Actor model is primarily about concurrency and isolation.
Kite is about control flow, ownership, and responsibility, even 
in single-threaded code.

Actor model:
You send a message to another actor
You don’t know who called you
You typically don’t return values directly
Everything is asynchronous (or mailbox-based)

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

Actors remove the concept of a caller.
Kite makes the caller central.

Another way to see it
Actor model → “No one owns the flow, messages drive everything.”
Kite → “The caller owns the flow.”

These are almost opposite design philosophies.

A more accurate positioning of Kite would be:

“An object-oriented language with explicit caller context and no 
hidden control flow.”

Or:

“Like OOP without static — where the caller is always in control.”