natalie VS fib

Since I tried Sorbet, a Ruby type-checker, the idea of building an ahead-of-time compiler for Ruby is a cool side project that has been in my mind for some time now. To my surprise, during Hacktoberfest, I got to know Natalie, this AOT compiler written in C++ by Tim Morgan.

Unlike other languages, ruby is mainly driven by one application - Rails. As newer web FWs come, it's hard to see Rails keep up. The trends for Rails does not look good for the past 5 years [1]. I am hopeful that natalie [2] will work. If it does, it will remove the biggest downside to ruby.

[1] https://trends.google.com/trends/explore?date=today%205-y&q=...

[2] https://github.com/natalie-lang/natalie

I've typically found rust to be about 100x faster than Python for the projects I've ported. This is consistent with https://github.com/drujensen/fib.

Here is a similar benchmark but includes compile times. https://github.com/drujensen/fib

How? Do you mean how do I know it's slow? Because it takes longer to run.

Write a typical computation such as Fibonacci in Java and Erlang/Elixir and compare. Fortunately someone has already done this.

Elixir is 3x slower than C and 2x slower than Java for this single thread example.

https://github.com/drujensen/fib

Apparently this upsets people for me to point this out. However, I did not say that Elixir was slow in general or a bad choice. It's an excellent choice for problems which suit parallelization or which require reliable, consistent performance.

Since the parent poster had commented that adding this multi-module dispatch would not be performant, I merely pointed out that the single thread peformance was already slow (as in, why worry too much about the performance cost of the multi dispatch suggestion).

Is there some advantage over repos that also show the results ?