helix

Or if you need both, Yehuda Katz's company Tilde made a library that can help you write code in Rust and use it in Ruby. So if there's a critical path in Rails that you need to speed up in Rust you can do that: https://www.youtube.com/watch?v=lBapt5YDDvg https://github.com/tildeio/helix

But abandoning everything you've written in one language for the sake of a single hot path isn't really a good idea either. It's probably a more sensible idea to use a native extension to optimize just that hot path. For instance, the Rust bindings are really good: https://github.com/tildeio/helix

Fortunately, you don't have to use C for this any more. Rust has bindings for making extensions for Ruby, Python, Lua and Node, and generally it's very well suited for making zero-cost cleaner APIs on top of C FFI. https://github.com/tildeio/helix https://github.com/PyO3/pyo3 https://github.com/kyren/rlua https://github.com/neon-bindings/neon

Rust can make .o files just fine. But yes, PHP had some of these types of tools (at least back in the day, haven't looked lately) for PECL extensions. Like Node, if it's C++ only or requires actual C source, writing glue is trivial, should have no performance cost, and is a way better option than completely switching WASM impl choices because of these limiting platforms. If you don't want to manually write this glue, there are often projects (like [0] for Ruby) that will help. Again, better than artificially constraining the implementation language. 0 - https://github.com/tildeio/helix

As others have mentioned, it's too slow for what the author was trying to achieve. He had a section where he ruled out cgo for performance reasons, so if that's too slow, spawning a child process will be much slower. That may not matter for your use case, but the author is clearly aiming for almost no overhead considering how easy it is to use cgo to call into Rust. The thing that should probably be said is that the difficulty is all on the Go side. Rust doesn't have any of the clumsiness that Go has when interacting with other languages. It's fully fluent in the lingua-franca of FFI (C ABI). If you were integrating your Ruby, Node or Python code with Rust instead of Go, there are nice libraries [1][2][3] that make it simple, easy and very low overhead. For users of these scripting languages, Rust is a nice tool to keep in your back pocke

Thoughts on replacing Arel with Diesel + Helix[0]? [0] https://github.com/tildeio/helix - When Helix can handle that complexity (if it can't already)

Yeah, we iterated a bunch on this question, and I still don't think we have it quite right. On the REPL side, we've had a few prototyped out [1] out over the years. We'd love something someday. What do you use for your scientific computing? We are also have some projects that are trying to ease using Rust with other languages ([2], [3]), so knowing what we should priorities would help. [1]: https://github.com/murarth/rusti [2]: https://github.com/rustbridge/helix [3]: https://github.com/rustbridge/neon

Interesting. Wonder how it compares to Helix [1]. https://github.com/rustbridge/helix

That's why it's exciting to see libraries like Helix[0], Neon[1], and Rustler[2] that help folks embed Rust into higher level languages safely. Opens lots of possibilities by making even those performance critical sections of code safe for a whole team to hack on. - [0]: https://github.com/rustbridge/helix - [1]: https://github.com/rustbridge/neon - [2]: https://github.com/hansihe/Rustler