Comment by giancarlostoro

11 hours ago

I think its written for people who already know what the BEAM is. The BEAM is the VM for Erlang or Elixir, similar to how Java has the JVM and C# has .NET essentially.

> similar to how Java has the JVM and C# has .NET essentially.

I'm pretty sure that in this analogy, C# has the CLR.

A lot of people know that Beam is an open-source unified programming model for defining data processing pipeline, both batch and streaming (B[atch and Str]eam), in a way that’s portable across different execution engines. That's why people are asking to clarify what Beam is before sending us to watch the conference recordings.

  • I think there are plenty of context clues in the first few sentences.

    > ... fascinated with BEAM, how it allowed easy spawning of processes ...

    > ... the appeal of BEAM languages ...

    > ... haven’t read The BEAM Book yet ...

    > ... examples are written in Elm ...

    • Those context clues do nothing for people who have no idea about BEAM but know about Beam and just think it's an uppercase version of it.

      > ... fascinated with BEAM, how it allowed easy spawning of processes ...

      beam runner spawns worker processes very easily

      > ... the appeal of BEAM languages ...

      You can write Beam workflows in Java, Python, Go and Scala

      > ... haven’t read The BEAM Book yet ...

      https://www.amazon.com/Streaming-Systems-Where-Large-Scale-P...

      > ... examples are written in Elm ...

      Hm, maybe they added Elm SDK for the Beam, but why?...

      8 replies →