Hi everyone! I am looking for a new role and would appreciate your support. Lately I've been working mostly with functional languages (#Elixir, #Erlang, #Haskell, #Elm) in web development, but I'm also passionate about programming languages and tooling (compilers, static analysis, development environments, etc). Let me know if you see an opening that you think I may enjoy!
Found a nice talk on concurrency. It has a very brief comparison of different concurrency models, like Erlang's Actors, Hoare's CSP, Go's goroutines, Clojure's core.async, Concurrent ML (aka Fibers in Guile).
Primary focus on Concurrent ML (but examples are in Scheme with type annotations ><).
I would argue than #Erlang is more suitable for writing compilers than #CommonLisp just because it has built-in pattern matching, tuples and map literals. Clojure got literals right but no pattern matching. Oh and DESTRUCTURING-BIND in CL does not count.
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.
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
It is incredibly tempting to interpret and implement ActivityPubs concept of an Actor as an Elixir GenServer/actor. Mailboxes and message passing.
If I was building it out as an in-memory system this could be fun but for typical needs it is conflating runtime characteristics with the outward protocol.
Lining those up would make the system simple to reason about in particular ways. I might do the experiment.
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.
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.
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