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.