Re:What's all this fuss about Erlang? (2007)
by lliamander on Tuesday January 24, 2017 @04:04PM
(#13475423)
> Go is probably the closest thing, and it's still lacking some things like the supervision tree.
From what I've read, Go's runtime just isn't compatible with the kind fault-tolerance that Erlang provides (nor was it meant to). It lacks process monitoring, lacks process isolation, has a pause-the-world garbage collector, etc.
Not a knock against Go, just pointing out that the design goals were different.
Re:What's all this fuss about Erlang? (2007)
by djKianoosh on Tuesday January 24, 2017 @03:17PM
(#13475058)
so many people (including me from time to time) misunderstand "computaionally expensive" that I think Elixir/erlang/beam will serve a lot of systems/apps well for a long time until they really see a need for "intense" computation
Re:What's all this fuss about Erlang? (2007)
by davidw on Tuesday January 24, 2017 @04:33PM
(#13475738)
Oh, absolutely - you can do tons of things with Erlang, just as people do with Ruby, Python, PHP, Tcl, etc...
But that article is a bit hype-y.
Re:What's all this fuss about Erlang? (2007)
by djKianoosh on Tuesday January 24, 2017 @05:06PM
(#13476123)
well, of course it is ;) consider the source.
A lot easier said than done, because there are a lot of really fundamental decisions about Erlang that make it what it is. You can't just slap on a scheduler for instance, or Erlang style processes.
Go is probably the closest thing, and it's still lacking some things like the supervision tree.
Erlang is certainly not 'the answer' in terms of computationally intensive anything, for the foreseeable future.