3 ms·
I would insanely choose ruby rather than javascript for the major advantages that has to offer. Performance in most of cases is not a real needed over consisten
by lovelle 8y ago
I would insanely choose ruby rather than javascript for the major advantages that has to offer. Performance in most of cases is not a real needed over consistency. Also Ruby 2.6 has jit, would be great to see some bench tests. :P
- abhorrence 8y ago2.6’s JIT is entirely at the method level currently, and unfortunately for certain types of workloads (e.g. Rails) this means the performance benefit is largely outweighed by the call counters and deoptimization checks on every method invocation. There’s definitely room for improvement, and the inclusion of JIT infrastructure is awesome, it’s just not making much of a performance impact. Yet.
- munificent 8y agoV8 is also a method-based JIT as far as I know.
- jashmatthews 8y agoThe overheads from the call counters and deoptimization checks are tiny. The real problem is that right now MJIT doesn't allow much optimization beyond generating native code equivalent to simply executing the instructions. It's ridiculously simple compared to V8.
- windows_tips 8y agoIsn't there a Ruby->JS transpiler?
- ukz 8y agoOpal: https://github.com/opal/opal https://github.com/opal/opal
- tlrobinson 8y agoOut of curiosity, what are the major advantages Ruby has to offer over JavaScript?