Earlier quoted context omitted.
> I'm pretty sure Go is going to eat Erlang. I wouldn't be surprised by this. Go's concurrency pattern is fantastic, but to match what Erlang does it needs to be easily extended beyond the running process. Can channels connect multiple "nodes" yet? That is, two running go programs, can they communicate via channels or do they have to use some other IPC mechanism? Across a network? That universal communication structu…
> I wouldn't be surprised by this. Go's concurrency pattern is fantastic Only for those not versed in java.util.concurrent, TPL, PPL, TBB, Cilk Plus.
Ask HN: Why isn't Erlang more popular?
241–244 of 244 posts
Re: Ask HN: Why isn't Erlang more popular?
#242Earlier quoted context omitted.
Why, because all programming endeavours are equally hard or important, and all programmers have equal skills?
In this make believe scenario, the world is divided neatly into opposing camps of "competent devs" and "enterprise CRUD devs". It's dismissive, cheap analysis at its best. It's a straw man whose only real purpose is to embolden us with a smug sense of superiority.
I've worked for enterprise.
Also I didn't say it is divided "neatly". Why do people always assume that when you talk about a group of people being Y, all of them must be Y?
It's enough that the statistical majority of them be Y (e.g 90% of enterprise developers not really knowing about the wider world outside enterprise software practices). That there will be exceptions it's obvious -- there are exceptions everywhere.
Re: Ask HN: Why isn't Erlang more popular?
#243A language needs to get a foothold somewhere. Ruby started on the low end and worked its way into a position of power. Java started in the enterprise and became normal thanks to catering to their needs so well. Erlang is in an awkward place where it solves certain problems well, but there is not a big class of user for it to get a foothold in. It's not better than Ruby at bring Ruby and it isn't better than Java at b…