> And this explains why Erlang hasn't conquered the world. I suspect the reasons are less technical than marketing, timing, etc. It takes some experience to ap

> And this explains why Erlang hasn't conquered the world. I suspect the reasons are less technical than marketing, timing, etc. It takes some experience to appreciate what it does - it's not an obvious sell like "get a webapp going in 30 min" can be for Ruby. Although Elixir/Phoenix are doing some amazing things to fix that :) OS processes are a fine way to isolate concurrent processes if they're quite granular. It works less well when there's 10000 of them (e.g. websocket connections), and they want to share a DB connection pool, metrics, etc.