io VS pony-tutorial

Second for smalltalk, also IOLang is super great, and of course the mighty Lua

Hope they will add this link on the site: https://github.com/IoLanguage/io/tree/master/samples/misc

Io and Rebol both have homo-iconicity and a macro system. Would you call them a Lisp? The name "Lisp" is short for "Lisp Processing". No wonder Lisp is the most powerful language in the world, when all powerful languages are secretly Lisp without knowing it!!!

https://iolanguage.org/

For oo/meta I'm partial to IO: https://iolanguage.org, is pretty neat to see how prototypal OO works.

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...