Andrea Leopardi
andrealeopardi.com · Personal blog · on HN since 2016
Andrea Leopardi, an Elixir core team member, writes about Elixir, Erlang/BEAM, networking, libraries and testing.
What HN saysHN cites his posts on retiring the short_maps library over clarity regrets and on using NIFs to run native code from Elixir.
18HN people shared it
2linked it in comments
18stories submitted
45story points
3 months agolast shared
2016people per year2026
Most-shared posts
- 1Get Rid of Your Old Database Migrations4 people · 8 points · first shared 2022 · 2 comments on HN
- 2RPC over RabbitMQ (With Elixir)3 people · 8 points · first shared 2020 · discussion on HN
- 3Handling TCP connections in Elixir2 people · 11 points · first shared 2016 · discussion on HN
- 4Using C from Elixir with NIFs (2015)2 people · 3 points · first shared 2017 · discussion on HN
- 5A story of regret and retiring a library from hex2 people · 1 points · first shared 2018 · discussion on HN
- 6Beam Metrics in ClickHouse1 people · 3 points · first shared 2026 · discussion on HN
- 7A Breakdown of HTTP Clients in Elixir1 people · 3 points · first shared 2023 · discussion on HN
- 8The guts of a property testing library in Elixir1 people · 3 points · first shared 2017 · discussion on HN
- 9Elixir's GenStage Demand, a visual explainer1 people · 2 points · first shared 2026 · discussion on HN
- 10Process Pools with Elixir's Registry1 people · 1 points · first shared 2023 · discussion on HN
- 11Counting Fast in Erlang with:counters and:atomics1 people · 1 points · first shared 2026 · discussion on HN
- 12(Erlang VM) Persistent connections with gen_statem1 people · 1 points · first shared 2023 · discussion on HN
What HN people wrote when they linked it
jzimbel · 2024-05-12
This was done previously with the `short_maps` library, which the author—a member of the Elixir core team—eventually retired and archived due to regrets from the undesirable impacts on clarity.
https://github.com/whatyouhide/short_maps https://andrealeopardi.com/posts/a-story-of-regret-and-retiring-a-libr…
sasa555 · 2017-01-27
It is possible to start external processes from BEAM and interact with them. I've blogged a bit about it at http://theerlangelist.com/article/outside_elixir
You can also write NIFs (native implemented functions) which run in BEAM process (see http://andrealeopardi.com/posts/using-c-from-elixir-with-nifs/). The latter option should be the last resort though, because it can violate safety guarantees of BEAM, in particular fault-tolerance and fair scheduling.
So using BEAM facing language as a "controller plane" while resorting to other languages in special cases is definitely a viable option.