theBeamBook
erjang
| theBeamBook | erjang | |
|---|---|---|
| 7 | 2 | |
| 3,044 | 723 | |
| - | 0.8% | |
| 5.8 | 10.0 | |
| about 1 month ago | about 6 years ago | |
| Erlang | Java | |
| Creative Commons Attribution 4.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
theBeamBook
- Ask HN: Programming Courses for Experienced Coders?
-
Erlang/OTP: Garbage Collector
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!
-
Lunatic is an Erlang-inspired runtime for WebAssembly
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...
-
Log 2022-10-19
theBeamBook repo
-
Will project loom make java concurrency comparable to erlang's?
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!
-
How are processes scheduled
Check the https://github.com/happi/theBeamBook/blob/master/chapters/scheduling.asciidoc
-
What is your opinion on Ada? Have you used it for embedded development? When did you use it?
Did you find this? As far as I know, it is the best resource: https://github.com/happi/theBeamBook
erjang
-
Erlang/OTP: Garbage Collector
Almost 10 years ago, i've tested erjang [1] using a medium sized application. Throughput was better than BEAM but latency was terrible.
[1] https://github.com/trifork/erjang/
-
Type-Based Optimizations in the JIT
You could, and in fact there has been Erlang implementations on top of the JVM[1][2], however you will never be able to get the same runtime characteristics of Erlang running on BEAM due to the fundamental differences in memory management: BEAM is first and foremost designed for reliability, predictability and soft real-time behaviour.
[1] https://github.com/trifork/erjang/
What are some alternatives?
chat - A telnet chat server
erlt - Early prototype of ErlT, an experimental Erlang dialect with first-class support for static typing.
jerlang - Erlang/OTP on the Java Virtual Machine (JVM)