1. For sure, "fast" is a bit of a vague term. To be more specific it's not fast at number crunching, but it has a low latency, low standard deviation concurrent

1. For sure, "fast" is a bit of a vague term. To be more specific it's not fast at number crunching, but it has a low latency, low standard deviation concurrent garbage collector and it's quite memory efficient. More details can be found online, and WhatsApp etc provide some good case studies. 2. Yes! More documentation will come as the language matures. For now we will have to defer to Erlang and Elixir documentation and studies. 3. All three. Gleam aims to provide scalability with development through excellent tooling and static analysis, Erlang and the VM provide runtime scalability with fault tolerance, concurrency, parallelism, and distribution at runtime. 4. Quite a tricky one to explain quickly but it's concurrency model based around the idea of having many sychronous subsystems working together in a system similar to how people work together. It's often said to be one of the easiest to use concurrency models. To paraphrase one of Erlang's creators: "It's hard to write a web server that can process 1000,000 concurrent requests, it's easy to write a web server that can handle 1 request and run 1000,000 of them". 5. Most languages will only have 1 thread or 1 per CPU on the machine, so having millions is quite unusual. Golang is another language that has this property and it has proven very valuable. 6. I'm sorry, I don't understand this question. What do you mean? 7. It's not analysis, so turning completeness isn't an issue! The fault tolerance is purely a runtime behaviour. It covers exceptions and such, but also works for hardware failure, network issues, memory corruption, etc.