It looks like a nice language with the {} syntax to tease all the C and Java developers out there. That's more important than it looks to help spreading the language.

The OTP example lets me state one of my few sore points about all the BEAM languages I worked with or looked at: the handle_this / handle_that madness. Search for "type AsyncTaskMessage" in the post to get there.

I don't want to write code like this (I omit the details, ... are ellipsis from mine)

  type AsyncTaskMessage {
    Increment(reply_to: Subject(Int))
    Decrement(reply_to: Subject(Int))
  }

  fn handle_async_task(message ...) {
    case message {
      Increment(client) -> {
        code ...
      }
      Decrement(client) -> {
        code ...
      }
      ...
   }

I want to write code like this

  type AsyncTaskMessage {
    Increment(reply_to: Subject(Int))
    Decrement(reply_to: Subject(Int))
  }

  fn Increment(client) {
    code ...
  }

  fn Decrement(client) {
    code ...
  }

or any variation of that, maybe this OO-ish one (after all this is a stateful object)

  type AsyncTaskMessage {
    fn Increment(reply_to: Subject(Int)) {
      code ...
    }

    fn Decrement(reply_to: Subject(Int)) {
      code ...
    }
  }

Maybe one of the next BEAM languages will handle that automatically for us.