pony-tutorial VS Carp

I don't think that there is a book written about Pony, but the tutorial and the list of patterns (WIP) are all you need to learn the language.

[Pony](https://tutorial.ponylang.io/): actors, reference capabilities, object capabilities.

Pony is a relatively young but interesting language with capabilities-security.

Well, depends on how you define ownership. Pony 's type system has reference capabilities which let you define who's allowed to do what to a reference and part of it sort of deals with ownership (along the lines of "this actor is allowed to do Y to the reference, other actors are allowed to do Z"). You can eg. have methods that return an isolated value that guarantees that there are no other references to that value, meaning it's automatically thread safe. You can also define things as vals which says that they are globally immutable, refs which give the current actor read/write capabilities but can't be shared with other actors

The alternatives are:

- Division must be impure (because it can throw an exception)

- Division must be partial - i.e. return Option[Int].

Both seem worse compared to defining division by zero as zero. Coq, Lean, and Pony do the same. https://github.com/ponylang/pony-tutorial/blob/master/conten...

Carp - https://github.com/carp-lang/Carp - "A statically typed lisp, without a GC, for real-time applications." where it's "Ownership tracking enables a functional programming style while still using mutation of cache-friendly data structures under the hood".

Looking for a personal project so open-source would be great, but maturity/production readiness is not really a factor.

The only significant thing i can find so far is https://github.com/carp-lang/Carp.

Anything notable that i might have missed ?

Not CL, but there is ulisp (http://www.ulisp.com/) for microcontrollers, supposed to be really tiny, and there is Carp (https://github.com/carp-lang/Carp) which is without a GC so seems suitable for real-time stuff.

by their powers combined

Everybody is trying to make a more user-friendly Rust. The problem is that it is not clear yet whether that's possible, and if it is, how it may look. I know Vale and have tried it, though it's extremely early to judge anything so far. It does have a much stronger theoretical background than V, but even the theory is not completely clear at this point.

There is also Carp by the way: https://github.com/carp-lang/Carp