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.
@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.
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.
This blog post points out that automatically restarting processes can hide problems, which is certainly true. Doesn’t have to be systemd. Something like supervisor trees in #Erlang/#OTP might do the same.
If you’re restarting something, measure restarts and plot them on a graph. If it’s happening, understand why it’s happening. If it’s designed to fail, fail it on purpose at a regular cadence to make sure that failure is being compensated for correctly.
I'm trying to get into functional programming and am looking for audio resources that are interesting/helpful to listen to while driving/doing other things. I would prefer something that talks about functional programming in general and the concepts or that is haskell-oriented, but i'm open to all resources. Thank you!
#bitsyntax: a binary pattern matcher inspired by #Erlang's (which is an incredible feature that every language should consider implementing) for #racket
The s390x open source team at IBM confirms the latest versions of various software packages run well on #Linux on #IBMZ. In October 2023 validation was maintained for over two dozen projects, including: the #Apache web server, #ApacheCamel & #Erlang
If #Erlang wasn't dying out, I'd want to learn more and seek work. The world's largest telephony over ATM network ran on Erlang and had 9 nines (!) of availability. That's 31 milliseconds of downtime per year.
Part of why it was so reliable is that it's a language which basically makes you write #microservices for all functionality, but with much of the infrastructure support built in. What an amazing technology.
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 🔮
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.
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
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.