I&#x27;ve been using Erlang on and off since 2003, and used it heavily at the last place I worked to build a pretty cool product, so I&#x27;m a fan.  That said, this article is a little bit hypey, although it&#x27;s all correct as far as I can see.<p>* I&#x27;d still build most products in Rails, because there is <i>so</i> much ecosystem that lets you get something up and running quickly.  The exception being if I absolutely knew that the system had to aim for really big numbers from the get-go (which is not the kind of market I&#x27;m particularly even interested in these days), or had to be super-reliable, or some kind of semi-embedded system like what I did in the last place I worked.  I loved Joe Armstrong&#x27;s answer here: <a href="http:&#x2F;&#x2F;erlang.org&#x2F;pipermail&#x2F;erlang-questions&#x2F;2015-October&#x2F;086379.html" rel="nofollow">http:&#x2F;&#x2F;erlang.org&#x2F;pipermail&#x2F;erlang-questions&#x2F;2015-October&#x2F;08...</a> - &quot;My goal would be to get something up and running as soon as possible and get users - and not worry about implementation details.&quot;<p>* By the same token, if you <i>know</i> you need something with raw computing speed, Erlang isn&#x27;t it either, as the article mentions.  Although it&#x27;d certainly be possible for Erlang to farm out work to something faster, if the additional architectural complexity isn&#x27;t a problem.