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

[Marconi]

On Friday, 1 May 2026 at 02:55:40 UTC, Araq wrote:
> On Friday, 1 May 2026 at 01:57:57 UTC, Marconi wrote:
>> Curious to hear thoughts — especially what breaks in this 
>> model.
>
> It's not about what "breaks" in this model, it's about what 
> works in this model. What works: Hardly anything. How does the 
> system know when to call on_delete now that the compiler is 
> responsible for on_new?
>
> But since you used AI to write your post (easy to tell) you 
> might as well use more AI to find all the flaws in your ideas. 
> Good luck.

You’re right — on_delete was a mistake.

We only need explicit deallocation:

delete obj;

Kite may hide where memory is allocated, but it never hides when 
it is freed.

It separates allocation from lifetime, which is different from:

C (everything manual)
GC (everything automatic)
Rust (everything tracked)

Kite is a different hybrid model.

If you forget delete, you get a memory leak — by design.