> [T]he JVM excels at computational work compared to the BEAM.
What sorts of scales are you talking about when you refer to "computational work"?
Also, was/were the comparison(s) you're referring to being done using native code?
You can also compile Elixir and Erlang to native code if you want it to run computational stuff faster...
> You can also compile Elixir and Erlang to native code
How? Can you provide a link about this?
Add this at the top of your module (in Elixir):
@compile [:native, {:hipe, [:verbose, :o3]}]
:-o
Hi forgot about HiPE :-)
But it doesn't produce a native binary, does it?
Where did I claim it did?
Nowhere :-) I read too fast and mistakenly assumed native code = native executable binary.
Is using HiPE a standard practice in the Erlang/Elixir community? What is the quantitative performance gain?
Re:Elixir v1.3 released
by lucidstack on Thursday June 23, 2016 @07:52AM
(#11960265)
This comment from Reddit sums it up pretty well: https://www.reddit.com/r/elixir/comments/3gd1n3/what_are_the...
I just discovered about HiPE as well, and I just gave it a try with a simple fibonacci module. Running fibonacci(40) went from 3.9s BEAM to 0.7s HiPE.
I know it's a silly test, but it's pretty sweet to witness such a massive difference out of the box. :)
BEAM has many great advantages such as fault tolerance and multi-node distribution built in. This allows concurrency to be a first-class citizen for applications running on the BEAM. I'm not saying that concurrency can't be done on the JVM, but that I've found it to be much simpler using BEAM. On the other hand, the JVM excels at computational work compared to the BEAM. Both VMs have their place and can be better at different types of problems comparatively.