Future of Rune #973
Replies: 1 comment 2 replies
-
|
Hi, and thanks for the kind words! Rune is a hobby project. I spend some time working on it whenever I find it, but in terms of maturity you shouldn't expect anything. There are bound to be significant issues which means you must never feed it fully untrusted code like the compiler likely be coerced to run out of memory and crash the service. Just to give a rough idea. There are quite a few blockers for a 1.0 release, but I don't have an exhaustive list beyond the issues marked as My recommendation would be to use v8 if you are accepting untrusted code, which has been designed from the ground up to deal with sandboxing of untrusted code. There are a few wasm runtimes in Rust, but I'm personally not convinced they are mature enough to rely on. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Rune is an awesome project. It’s not finished yet, but even now it’s really impressive.
We’re working on a new startup and trying to pick a language for running user-submitted code safely. We looked at Lua, Rhai, and QuickJS, but Rune really stood out. It’s async, lightweight compared to WASM and QuickJS, and just feels simple and well thought out.
Right now, we’re at the decision stage and had a few questions:
We’re genuinely interested in using Rune and would love to know where things are headed.
Beta Was this translation helpful? Give feedback.
All reactions