For a new podcast I'm looking for guests from marginalized and underrepresented groups in the #elixirlang / #erlang / #BEAM community.
My co-host Adi Iyngar and me are looking to shine a light on the lived experiences of these communities. We're more than the tech we use and far too often folks are not able to bring their whole selves. This podcast is meant to be our little contribution towards changing that!
I am looking for a new job. Elixir/erlang SWE and/or ops/SRE related. Size of the company does not matter. I have some ethical rules (gambling, blockchain and probably most AI company,...). I only work remotely from France. Yes I would prefer a FTE french contract, but I can do self employed contracts.
Don’t miss the chance to participate in the Erlang Workshop!
The Erlang Workshop brings together the open source, academic, and industrial communities of Erlang, other BEAM-related languages, actor model programming, distribution, and concurrency to discuss techniques, technologies, languages, and other relevant topics.
Important dates:
Paper submission: May 30
Notification: June 27
Camera Ready: July
It's fascinating to me looking at beginning language guides and thinking "what does this say about the culture of the language"
When I was delving into #OCaml it was (with affection) "here's hello world and here's a dense academic paper on implementing event systems in OCaml 5!"
#Java guides used to be centered on the assumption that you were a web programmer looking to do applets, even long after that assumption died.
#RustLang generally seems to assume a background in programming w/ a CLI.
Thinking about cultures of languages for a second:
My experience with #Erlang people (not elixir, I have only limited experience with elixir and less with the community) is that you were looking at practical people with a hard problem to solve, some niche elements to that problem, and who didn't get hung up on niceties (like having strings cough).
There's a massive degree of enthusiasm for the model and everyone kind of glossed over the language because of the runtime and model.
@hrefna I know syntax matters to people (and I haven't yet written #Erlang, only some #Prolog), but it is just a language. Just pattern-matching and immutability make it better than most by a long shot. So, I think the Erlang inventors got the language quite all right, and Elixir might just be a nicer way to write OTP style.
Join @codebeamio to celebrate the 30th anniversary of the Erlang/OTP User Conference!
Don't miss the insightful talk: Documenting Erlang/OTP ⌨
In Erlang/OTP 27 a new way of documenting code will be added, documentation attributes. @garazdawi will go through what the new documentation attributes look like, what makes it different from what we had before and how it may effect your project.
Join Kiko Fernandez and Ingela Andin in their talk at @codebeamio!
As Erlang/OTP developers for Ericsson and the Erlang/OTP team, they will provide insights into the history of Erlang/OTP, focusing on what happened after it became open source.
We’re joined by Louis Pilfold, creator of the Gleam programming language!
We discuss Gleam's inspiration, how it compares to other languages, where it shines, the overwhelming support Louis is getting through GitHub Sponsors & what’s next 🔮
If anyone in the #erlang community has been using the rich compiler error option in Rebar3 over the last year, I’m looking for any feedback or opposition before turning it on by default in the next release: https://github.com/erlang/rebar3/pull/2881
Been learning Erlang a lot at the same time (one could say...concurrently 🤪). Regarding syntax and language decisions, I find it much more approachable and consistent. Maybe more verbose (as the author of this book asserts), but I think I generally prefer that if we're not talking about extremes
A critical vulnerability, named BatBadBut, was discovered in the Rust programming language, affecting not just Rust but also Erlang, Go, Python, Ruby, and potentially others. This vulnerability, with a severity score of 10/10, could allow attackers to execute arbitrary commands on Windows systems by exploiting how Rust handles batch files. The issue arises from Rust's standard library improperly escaping arguments when invoking batch files on Windows, leading to potential command injection. The vulnerability has been addressed with a fix in Rust version 1.77.2, which developers are urged to update to. Other programming languages and systems, including Node.js, PHP, and Java, are also affected and are working on patches.
I love the ideas in #Erlang, but I’ve never quite gelled with the language. So when I heard someone was porting the runtime to #OCaml, my ears pricked up.
Leandro Ostera joins me this week to explain how he's borrowing BEAM's best bits. 😅