But .. your language mostly hide when you're doing an 'inside' function call or an 'external' function call. I'm not sure I like this; 1) the latency of both operation is very different so you want to minimise the number of 'external' function calls 2) what happens in case of 'timeout' for external function calls? I didn't see it in the doc, did I miss it?

ps: were you looking at efforts such as clojure electric (https://github.com/hyperfiddle/electric) ? they aim to represent computation on different hosts as one expression.

Most of the important stuff is in this section:

```3. What's Actually New About It?```

But you don't really go into any details about what's actually happening, have any honest conversation about any trade-offs, mention anything about why this is memory safe & correct now (highly skeptical), or why you have a clear path towards that in the near future.

From the VERY brief examples you show, it looks like it's just Rust without a borrow checker. The borrow checker gives Rust a bad reputation, but it's only a very small part of why Rust is hard. You didn't give any insight into how you're solving the rest of the problems.

https://hale-lang.org/articles/claims-in-hale/

Is choreographic programming the same as session types?

Can you you give a hello world example in each of them and show where your languages shines?

Is mut a thing? looks like rust.

https://felix-tutorial.readthedocs.io/en/latest/intro_corout...

Note this is for cooperative threading.