3 ms·
“Just throw a compiler at it!” If you really want a speed bump then that’s exactly what you want to do. And I think Ruby’s overlooking a golden opportunity to
by transfire 4y ago
“Just throw a compiler at it!”
If you really want a speed bump then that’s exactly what you want to do. And I think Ruby’s overlooking a golden opportunity to join forces with Crystal.
- basilgohar 4y agoThis is not true at all. Unoptimized, sloppy code will still leave a lot of performance on the table, whether compiled or interpreted. You might speed it up, but you'll still have problems scaling and your external services will still be hit just as hard (e.g., excessive queries vs. intelligent ones).
- Banana699 4y agoI generally agree with you that compiling to machine code is not a magic wand, code that does more is always slower than code that does less in a fair fight. But interpretation adds additional overhead to make slow code even slower, the more complex\unoptimized the interpreter the more it adds overhead. It's good for a language to have a baseline expectations of "Don't make things worse", shit code will always be slow, but at least it's not made slower by things outside of the developer's responsibilities.
- pjmlp 4y agoThat is what a JIT is, a dynamic compiler.