Re:Moving from Ruby to Rust
by jashmatthews on Thursday February 14, 2019 @07:33PM
(#19167509)
> There is simply no way of knowing enough to optimize when compiling a python script comparing to rust for example.
JIT with type specialization can do exactly that. It's all about whether the runtime cost is worth it.
Re:Moving from Ruby to Rust
by gchamonlive on Thursday February 14, 2019 @08:39PM
(#19167822)
Comparable to rust in terms of type level optimization? I am extremely curious about this and I want to know more, can you provide me with references?
Re:Moving from Ruby to Rust
by jashmatthews on Friday February 15, 2019 @04:55AM
(#19169689)
The JS JIT in WebKit used to use the same LLVM backend as Rust: https://webkit.org/blog/3362/introducing-the-webkit-ftl-jit/
This is one of the classic papers on type specialization in JIT: http://www.cs.williams.edu/~freund/cs434/gal-trace.pdf
Re:Moving from Ruby to Rust
by gchamonlive on Friday February 15, 2019 @07:02AM
(#19170177)
That is really cool thanks! I'm going to start reading
There is simply no way of knowing enough to optimize when compiling a python script comparing to rust for example.
Language depth has a cost though in terms of raw productivity, that is why there are languages like matlab that are there simply for prototyping and nobody in their right mind would use it for production purposes