beam_languages VS theBeamBook

Languages, and about languages, on the BEAM: https://github.com/llaisdy/beam_languages

PS: You might also find this interesting : https://www.grisp.org/

I thought this was a call for Standard ML or something a rather on the Erlang VM.

(I really enjoyed this article though!)

As far as I know theres a few implementations of ML like languages on the Erlang VM

https://github.com/llaisdy/beam_languages

caramel and alpaca are worth checking out.

Gleam doesn't look like a ML lang but has a lot of the same semantics of a ML lang

Have I got a link for you!

https://github.com/llaisdy/beam_languages

See you down the rabbit hole!

Elixir, LFE, etc. seem to work fine for the people who enjoy them.

https://github.com/llaisdy/beam_languages

LFE is Virding's himself, and has been around for longer than Erlang has been popular: Robert Virding - LFE - a lisp flavour on the Erlang VM (Lambda Days 2016) https://www.youtube.com/watch?v=Br2KY12LB2w

The Beam Languages repo is filled with projects to build on top of Erlang and the BEAM to take inspiration from.

It's my understanding the state of the art in observing JVM-based applications is a combination of using thread dumps, gc logs, thread activity visualizations. Thread dumps give us a snapshot of the the name of the thread, its current running state (waiting, blocked, etc), and the stacktrace of the work its currently doing. GC logs give you a record of when and how much garbage was collected and Thread activity visualizations show you the timeline of thread moving between different running states.

The BEAM gives you the ability to see the bottlenecks in your system, via the REPL (in real time!)

It has world-class introspection built in that gives you the power to observe and manipulate your running application through a REPL.

The BEAM has hundreds of features like this, because the BEAM is more of an OS than and VM.

I get it, you're a JVM expert, but the BEAM is more than a check list of optimizations that on paper the JVM can do.

I strongly suggest, before the next time you comment on an BEAM VM vs.JVM debate, please consider watching https://www.youtube.com/watch?v=JvBT4XBdoUE, "The Soul of Erlang and Elixir • Sasa Juric • GOTO 2019"

and reading https://github.com/happi/theBeamBook " an attempt to document the internals of the Erlang runtime system and the Erlang virtual machine known as the BEAM."

Best of luck!

it does. values are immutable in the BEAM, not at language level.

The impact of bugs is minimized by compartmentalization. This is done from the lowest level where each data structure is separate and immutable [1]

But you can simulate mutability with stateful processes.

Directly from Joe Armstrong: https://joearms.github.io/published/2013-11-21-My-favorite-e...

[1] https://github.com/happi/theBeamBook/blob/3971e8e2d09e367670...

theBeamBook repo

On a side-note, if you're really interested in grokking the BEAM itself, https://github.com/happi/theBeamBook is a very good resource that delves deeper into the internal working of BEAM. Regardless of whether you use it, it's a fun read!

Check the https://github.com/happi/theBeamBook/blob/master/chapters/scheduling.asciidoc

Did you find this? As far as I know, it is the best resource: https://github.com/happi/theBeamBook