Re: imagining a programming language with a capability calling convention

> If we're talking about memory safe languages, why lame?

paranoid hedging of bet. e.g. watch out for reflection?

> If creation does not violate the connectivity laws nor cause external
> effects, what's the problem?

uh, are those the case in bog-standard run-of-the-mill languages & environments?

i mean since there are projects to e.g. tame Java, Ocaml, JavaScript,
you name it, there are probably plenty of problems with our "standard
OOP" languages.