I've read more erlang than most of the elixir fanclub hackers will ever read or write. (granted elixir is a bit more terse, w/e) and I've shipped a functioning exploit that composed into RCE in a system that over twenty developers spent more than a decade designing, developing, and defending. Most of it was erlang. Almost all of it, really, except for some deployment routines and all the sql, etc.

I don't know the best way to solve problems, and I also don't know the very best problems that erlang is suited for, but large-scale web-oriented erlang is a mistake.

It's not that I want to hurt HNers feelings, it's just that I've literally seen this before. This whole thing is a rerun.

Just watch and see.

If it makes your booboo hurt any less, I think most elixir hackers are decently practiced hackers in general. If they had better beans, they'd make better coffee. The team I worked with were definitely top notch.

As for your question, I have no idea. I'm more of a problem spotter. My """solutions""" are generally of the "don't do this dumb thing" variety, with an accompanying exploit or kit or injection or whatever it is for that problem.