News for hackers. Stuff that matters.
Re:Elixir Design Goals (2013) by davedx on Saturday December 24, 2016 @08:26AM (#13249689)
This discussion is going in circles.

Fast at what?

From what I read, Elixir is very fast at I/O based tasks, especially when there is lots of blocking involved. For example orchestration layers that push data between various API's and/or handle many concurrent connections.

Languages that compile to the JVM like Scala or Clojure (or Java of course) will probably be faster for computation.

I see Elixir as being suitable for the same category of applications as nodejs.

Re:Elixir Design Goals (2013) by pmarreck on Saturday December 24, 2016 @09:37AM (#13249913)
> I see Elixir as being suitable for the same category of applications as nodejs

While being a hell of a lot saner.

https://www.quora.com/How-is-Elixir-Phoenix-better-than-Node...

Re:Elixir Design Goals (2013) by dozzie on Saturday December 24, 2016 @10:05AM (#13250025)
> From what I read, Elixir is very fast at I/O based tasks, especially when there is lots of blocking involved.

Now make two steps back and read this again. What you say is that Elixir is "very fast" when it comes to tasks when Elixir pretty much doesn't do anything, so it being fast or slow doesn't matter. Hardly a definition of "fast".

But it is actually true for BEAM machine. It was never intended to be fast, it was intended for running many tasks at the same time (so that none of them starves others for any reason).