I wrote a blog post about my ten years in Erlang, hype phases, adoption, things that changed, and I believe some of the content in there will be relevant to Elixir folks trying to boost adoption: Ten Years of Erlang

I’ve been posting the ones on Erlang-Battleground on this thread, lately.
Not sure if I should add them here as well.

Generally it’s best to stick to one thread - either your blog’s dedicated thread, or one of the main ones like this one

(As a side note, I am not completely happy with how we deal with blog posts on the forum atm, so we will be tweaking this at some point - watch this space )

Nice post! Heads to the ground; in the spirit of the erlang creators.

Which companies are using Erlang, and why? #MyTopdogStatus by Francesco Cesarini

Erlang was that badly kept secret. Many have heard of it, but few realise that it controls vast amounts of infrastructure, including the fixed and mobile networks we use on a daily basis.

Article:

Hi folks!

Building Caramel is teaching me a lot about Erlang and OCaml, so I figured I’d share some of these learnings with y’all

I’ll start with some thoughts on Why Typing Erlang is Hard (and what we can do about it).

Here’s part 1:

Sorry for the off topic question, I did not read the article yet, but I’ve just found about Caramel thanks to your post, I read the github README and I wonder why you chose to compile to .erl instead of compiling directly to .beam.

No problem I just thought it’d be a good starting point since:

• it is trivial to inspect that the outputs are correct, which makes it easy to see what’s going on, and that’s especially important when learning

• it is less of a hassle to just drop a little .ml into an existing project

Eventually I want to enable Core Erlang outputs, so you still get a shot at picking your compiler, but we can do some optimizations on the generated sources.

Providing .beam outputs would mean reimplementing parts of erlc that I’m not that familiar with yet. But I’m open to the idea

That makes sense, thank you.